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

upgrading to install jiva causes resource mapping not found #330

Open
si458 opened this issue Jul 11, 2023 · 0 comments
Open

upgrading to install jiva causes resource mapping not found #330

si458 opened this issue Jul 11, 2023 · 0 comments

Comments

@si458
Copy link

si458 commented Jul 11, 2023

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

@si458 si458 changed the title upgrading to install new engine causes resource mapping not found upgrading to install jiva causes resource mapping not found Jul 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant