Description of problem: As described in https://github.com/nmstate/kubernetes-nmstate/issues/729, multiple handlers may think they hold the lock. Version-Release number of selected component (if applicable): 0.44.0 How reproducible: Always Steps to Reproduce: 1. Deploy operator using CNAO 2. Create nmstate instance 3. Check handler logs Actual results: Multiple handlers claim to have the lock. Expected results: Only one handler takes the lock. Additional info: This fix was released in 0.46.0 upstream. We just need to rebase to that.
The linked PR is merged, moving to ON_QA.
It turns out I misunderstood the problem here when I opened the bug. The issue is actually that when you have two copies of the operator installed (say from OLM and CNAO or OLM and source) they don't properly coordinate locking. This means verification will require two copies of the operator installed. I've verified that this can be done with an install from OLM and from source, using the script in https://github.com/openshift/kubernetes-nmstate/pull/198 to deploy from source. Note that this scenario would not normally happen as you would only have one copy of the operator, but it is important to allow migration of existing CNV installations to the standalone operator.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.9.6 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:4119