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

Registry operator on vSphere gets Available=false during upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • 4.16
    • Image Registry
    • No
    • Rejected
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      CI permanently fails vmware-vsphere-csi-driver-operator-master-e2e-vsphere-ovn-upgrade jobs (and 4.15 and older too...)

      Example: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_vmware-vsphere-csi-driver-operator/220/pull-ci-openshift-vmware-vsphere-csi-driver-operator-master-e2e-vsphere-ovn-upgrade/1754552606383935488

      3/845 Tests Failed.[bz-Image Registry] clusteroperator/image-registry should not change condition/Available

      My guess would be that a pod managed by some Deployment is drained from a node, which causes the operator to report Available=false until a replacement one starts on another node. We have the same issue in one of storage team Deployments, OCPBUGS-29126.

      It could be related to the CI config, not sure why is this vSphere related.

              fmissi Flavian Missi
              rhn-engineering-jsafrane Jan Safranek
              XiuJuan Wang XiuJuan Wang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: