redhat-cop/group-sync-operator

configmaps lock is removed, migrate to configmapsleases

louise-zhang opened this issue · 12 comments

louise-zhang commented

CSV group-sync-operator.v0.0.21 install cannot be completed due to the below error:

unable to start manager {"error": "configmaps lock is removed, migrate to configmapsleases"}

image

ARO version: 4.10.15
Group sync operator: alpha: group-sync-operator.v0.0.21
group-sync-operator image: quay.io/redhat-cop/group-sync-operator@sha256:979acc20b045f1b21c5bb60bc3d95ed5ccb440d93eef9a4cbb19751d8922a83d

koolrays commented

Also seeing same issue.
ARO Version: 4.10.30
Group sync operator: alpha: group-sync-operator.v0.0.21
group-sync-operator image: quay.io/redhat-cop/group-sync-operator@sha256:979acc20b045f1b21c5bb60bc3d95ed5ccb440d93eef9a4cbb19751d8922a83d

sabre1041 commented

Issue acknowledged. Investigating....

sabre1041 commented

@koolrays @louise-zhang submitted #235

Will attempt to get a new release expedited

  • 👍7
vmospan-hub commented

Hi. When can we expect a new release with a fix?

sabre1041 commented

@vmospan-hub New release was just published and is being processed by the OperatorHub team

Release: https://github.com/redhat-cop/group-sync-operator/releases/tag/v0.0.22
Operator Hub PR: redhat-openshift-ecosystem/community-operators-prod#1984

  • 🚀4
vmospan-hub commented

Thanks!

sabre1041 commented

0.0.22 should now be available in Operator Hub

  • 🎉2
koolrays commented

Thanks for the quick turn around.

louise-zhang commented

Thank you @sabre1041, it's working now

ValentinoUberti commented

Thank you, @sabre104. It's working here using OCP 4.11.18 with RH IDM.

EirikOpheim commented

@sabre1041 We are stuck on Group Sync Operator 0.0.20 as the update to 0.0.21 failed with the error message described in this thread. What is the suggested way to get to 0.0.22? Do we need to uninstall and reinstall the operator or is there another way?
image

prgss commented

@EirikOpheim , we were in the same situation.

We removed both 0.0.21 and 0.0.20 and after that you can install again from scratch with 0.0.25 version.

image

Now the pod is running well.

Maybe there is an issue in the upgrade path, we should be able to bypass the 0.0.21 version when upgrading from 0.0.20