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

[ARO] 4.14 SDN to 4.15 SDN upgrading failed on multiple operators

    XMLWordPrintable

Details

    • Moderate
    • No
    • SDN Sprint 248, SDN Sprint 249
    • 2
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

      [ARO] 4.12.25 SDN to 4.15 SDN upgrading failed on multiple operators.

      Version-Release number of selected component (if applicable):

          

      How reproducible:

      Not sure  

      Steps to Reproduce:

      4.12.25 OVN -> 4.12.25 SDN -> 4.13.31-x86_64 SDN -> 4.14.10-x86_64 SDN -> 4.15.0-0.nightly-2024-01-25-051548 SDN (failed here)
      
      4.13.23 SDN -> 4.14.10-x86_64 SDN -> 4.15.0-0.nightly-2024-01-25-051548 SDN (failed here)
      
      4.12.25 OVN -> 4.12.25 SDN -> 4.13.31-x86_64 SDN -> 4.14.10-x86_64 SDN -> 4.15.0-0.nightly-2024-01-25-051548 SDN (failed here)
      

      Actual results:

      #### oc get clusterversion'                                                                ####
      NAME      VERSION   AVAILABLE   PROGRESSING   SINCE   STATUS
      version   4.12.25   True        True          127m    Unable to apply 4.13.30: wait has exceeded 40 minutes for these operators: etcd
      #### oc get co   --no-headers | grep -v '.True.*False.*False'                              ####
      authentication                             4.13.30        True    False   True    147m    APIServerDeploymentDegraded: 1 of 3 requested instances are unavailable for apiserver.openshift-oauth-apiserver ()...
      dns                                        4.13.30        True    True    True    3h35m   DNS default is degraded
      etcd                                       4.13.30        True    False   True    3h34m   ClusterMemberControllerDegraded: unhealthy members found during reconciling members...
      image-registry                             4.13.30        True    True    False   3h23m   NodeCADaemonProgressing: The daemon set node-ca is deploying node pods...
      kube-controller-manager                    4.13.30        True    False   True    3h32m   StaticPodsDegraded: pod/kube-controller-manager-weliang-aro1-9ptkt-master-0 container "cluster-policy-controller" is waiting: ContainerCreating: ...
      machine-config                             4.12.25        False   True    True    56m     Cluster not available for [{operator 4.12.25}]: failed to apply machine config daemon manifests: error during waitForDaemonsetRollout: [timed out waiting for the condition, daemonset machine-config-daemon is not ready. status: (desired: 6, updated: 6, ready: 5, unavailable: 1)]
      network                                    4.13.30        True    True    False   3h38m   DaemonSet "/openshift-multus/multus" is not available (awaiting 1 nodes)...
      node-tuning                                4.13.30        True    True    False   98m     Working towards "4.13.30"
      openshift-apiserver                        4.13.30        True    False   True    3h19m   APIServerDeploymentDegraded: 1 of 3 requested instances are unavailable for apiserver.openshift-apiserver ()
      storage                                    4.13.30        True    True    False   3h35m   AzureDiskCSIDriverOperatorCRProgressing: AzureDiskDriverNodeServiceControllerProgressing: Waiting for DaemonSet to deploy node pods...

      Expected results:

          

      Additional info:

          

      Attachments

        Activity

          People

            pdiak@redhat.com Patryk Diak
            weliang1@redhat.com Weibin Liang
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: