Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-57643

Network operator not updating due to missing release version annotation on whereabouts-controller and whereabouts-token-watcher

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • 4.20.0
    • 4.19.0
    • Networking / multus
    • None
    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Important
    • Yes
    • None
    • Proposed
    • CORENET Sprint 274, CORENET Sprint 275
    • 2
    • +
    • Done
    • Bug Fix
    • Hide
      Before this update, the Cluster Network Operator (CNO) stopped during a cluster upgrade where the `whereabouts-shim` network attachment was enabled. This issue occured because of a missing `release.openshift.io/version` annotation in the `openshift-multus` namespace. With this release, the missing annotation is now added to the cluster, so that the CNO no longer stops during a cluster upgrade where the `whereabouts-shim` attached is enabled. The cluster upgrade can now continue as expected. (link:https://issues.redhat.com/browse/OCPBUGS-57643[OCPBUGS-57643])
      Show
      Before this update, the Cluster Network Operator (CNO) stopped during a cluster upgrade where the `whereabouts-shim` network attachment was enabled. This issue occured because of a missing `release.openshift.io/version` annotation in the `openshift-multus` namespace. With this release, the missing annotation is now added to the cluster, so that the CNO no longer stops during a cluster upgrade where the `whereabouts-shim` attached is enabled. The cluster upgrade can now continue as expected. (link: https://issues.redhat.com/browse/OCPBUGS-57643 [ OCPBUGS-57643 ])

      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

       

              pliurh Peng Liu
              rhn-support-bverschu Bram Verschueren
              None
              None
              Weibin Liang Weibin Liang
              Darragh Fitzmaurice Darragh Fitzmaurice
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: