-
Bug
-
Resolution: Done
-
Major
-
4.18.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
1
-
Important
-
None
-
None
-
Rejected
-
CORENET Sprint 276
-
1
-
contract-priority
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
When uprading a cluster from 4.18.6 to 4.18.22, the CNO is stuck with:
Working towards 4.18.22: 739 of 903 done (81% complete), waiting on network
Both the "whereabouts-token-watcher" daemonset and "whereabouts-controller" deployment in the openshift-multus namespace are missing a "release.openshift.io/version" annotation.
During an upgrade, the CNO verifies this annotation [1] and halts the upgrade if that annotation is absent.
To workaround this, the CNO can be set unmanaged and the annotation set on the daemonset and deployment, afterwards the upgrade continues:
oc patch network.operator.openshift.io cluster --patch '{"spec":{"managementState":"Unmanaged"}}' --type='merge' oc annotate daemonset whereabouts-token-watcher release.openshift.io/version=4.18.22 -n openshift-multus oc annotate deploy whereabouts-controller release.openshift.io/version=4.18.22 -n openshift-multus
[1]https://github.com/openshift/cluster-network-operator/blob/2a1d6159a44bf8aa26bba9981f144006a1d99990/pkg/controller/statusmanager/pod_status.go#L114-L116
- clones
-
OCPBUGS-57643 Network operator not updating due to missing release version annotation on whereabouts-controller and whereabouts-token-watcher
-
- Verified
-
- depends on
-
OCPBUGS-60095 Network operator not updating due to missing release version annotation on whereabouts-controller and whereabouts-token-watcher
-
- Closed
-
- is duplicated by
-
OCPBUGS-60808 Network operator not updating due to missing release version annotation on whereabouts-controller and whereabouts-token-watcher
-
- Closed
-
- links to