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

CNO in HyperShift reports upgrade complete in clusteroperator prematurely

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • 4.13
    • None
    • Important
    • SDN Sprint 229, SDN Sprint 230, SDN Sprint 231, SDN Sprint 232
    • Rejected
    • Hide

      None

      Show
      None

    Description

      This is a clone of issue OCPBUGS-4350. The following is the description of the original issue:

      Steps to reproduce:
      Release: 4.13.0-0.nightly-2022-11-30-183109 (latest 4.12 nightly as well)
      Create a HyperShift cluster on AWS, wait til its completed rolling out
      Upgrade the HostedCluster by updating its release image to a newer one
      Observe the 'network' clusteroperator resource in the guest cluster as well as the 'version' clusterversion resource in the guest cluster.
      When the clusteroperator resource reports the upgraded release and the clusterversion resource reports the new release as applied, take a look at the ovnkube-master statefulset in the control plane namespace of the management cluster. It is still not finished rolling out.

      Expected: that the network clusteroperator reports the new version only when all components have finished rolling out.

      Attachments

        Issue Links

          Activity

            People

              pdiak@redhat.com Patryk Diak
              openshift-crt-jira-prow OpenShift Prow Bot
              Ross Brattain Ross Brattain
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: