Upgrade 3.7.0->3.8.0 fails when there exists a volumesnapshotclass about charts HOT 3 OPEN

I'm running into the same problem, when upgrading OpenEBS from 3.7.0 to 3.9.0, it's complaining there's already a volumesnapshotclass, however that's in a different namespace for a different storage class.

from charts.

Same issue with RKE2. Disabling the classes will bring another set of errors, although it the result is an OpenEBS that does work:

• echo 'Installing helm_v3 chart'
• helm_v3 install --namespace openebs --set-string global.clusterCIDR=10.42.0.0/16 --set-string global.clusterCIDRv4=10.42.0.0/16 --set-string global.clusterDNS=10.43.0.10 --set-string global.clusterDomain=cluster.local --set-string global.rke2DataDir=/var/lib/rancher/rke2 --set-string global.serviceCIDR=10.43.0.0/16 openebs openebs/openebs --values /config/values-01_HelmChart.yaml
  Error: INSTALLATION FAILED: 3 errors occurred:
  • customresourcedefinitions.apiextensions.k8s.io "volumesnapshotcontents.snapshot.storage.k8s.io" already exists
  • customresourcedefinitions.apiextensions.k8s.io "volumesnapshotclasses.snapshot.storage.k8s.io" already exists
  • customresourcedefinitions.apiextensions.k8s.io "volumesnapshots.snapshot.storage.k8s.io" already exists

from charts.

I'm seeing the same error when I deploy the lvm-operator like this:

kubectl create -f https://raw.githubusercontent.com/openebs/charts/gh-pages/versioned/3.10.0/lvm-operator.yaml

If I change from create to apply I don't get the error but I think that may just be masking the problem.

EDIT: the issue with rke2 is that it bundles snapshot-controller from upstream which conflicts with what OpenEBS is installing. rke2 bundled snapshot-controller can be disabled at install time, see: rancher/rke2-docs#123

from charts.