-
Bug
-
Resolution: Unresolved
-
Major
-
4.19.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
Yes
-
None
-
Proposed
-
CORENET Sprint 274, CORENET Sprint 275
-
2
-
+
-
Done
-
Bug Fix
-
When uprading a cluster to 4.19 with the whereabouts-shim enabled, the CNO is stuck with:
Working towards 4.19.0: 753 of 918 done (82% complete), waiting on network over 30 minutes which is longer than expected
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.19.0-rc.5 -n openshift-multus oc annotate deploy whereabouts-controller release.openshift.io/version=4.19.0-rc.5 -n openshift-multus
[1]https://github.com/openshift/cluster-network-operator/blob/2a1d6159a44bf8aa26bba9981f144006a1d99990/pkg/controller/statusmanager/pod_status.go#L114-L116
- blocks
-
OCPBUGS-60095 Network operator not updating due to missing release version annotation on whereabouts-controller and whereabouts-token-watcher
-
- Closed
-
- is cloned by
-
OCPBUGS-60095 Network operator not updating due to missing release version annotation on whereabouts-controller and whereabouts-token-watcher
-
- Closed
-
-
OCPBUGS-60795 Network operator not updating due to missing release version annotation on whereabouts-controller and whereabouts-token-watcher
-
- Closed
-
- links to