Skip to content
This repository was archived by the owner on May 8, 2024. It is now read-only.
This repository was archived by the owner on May 8, 2024. It is now read-only.

upgrading to install jiva causes resource mapping not found #330

@si458

Description

@si458

for some reason i cant seem to install the jiva engine AFTER i already installed the defaults with helm

the docs say that JIVA is installed by default when in fact, is not installed now by default through helm
https://openebs.io/docs/user-guides/installation#installation-through-helm
helm install openebs openebs/openebs -n openebs --create-namespace

so then afterward i try upgrading to install JIVA but get an error
helm upgrade openebs openebs/openebs -n openebs --set jiva.enabled=true --reuse-values

Error: UPGRADE FAILED: resource mapping not found for name: "openebs-jiva-default-policy" namespace: "" from "": no matches for kind "JivaVolumePolicy" in version "openebs.io/v1alpha1"
ensure CRDs are installed first

the only way to fix this is to uninstall the release then install again fresh with the values set
helm uninstall openebs -n openebs && helm install openebs openebs/openebs -n openebs --set jiva.enabled=true

EDIT: this issue seems to be related to the CRDs not being installed openebs-archive/jiva-operator#187 openebs-archive/jiva-operator#189

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions