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

control-plane-machine-set-operator is failing on AWS UPI

XMLWordPrintable

    • No
    • CLOUD Sprint 249, CLOUD Sprint 250, CLOUD Sprint 251
    • 3
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

       [sig-cluster-lifecycle][Feature:Machines] Managed cluster should [sig-scheduling][Early] control plane machine set operator should not have any events [Suite:openshift/conformance/parallel]

      Looks like this test is permafailing on 4.16 and 4.15 AWS UPI jobs - does this need to be skipped on UPI?

       

      {  fail [github.com/openshift/origin/test/extended/machines/machines.go:191]: Unexpected error:
          <*errors.StatusError | 0xc0031b8f00>: 
          controlplanemachinesets.machine.openshift.io "cluster" not found
          {
              ErrStatus: 
                  code: 404
                  details:
                    group: machine.openshift.io
                    kind: controlplanemachinesets
                    name: cluster
                  message: controlplanemachinesets.machine.openshift.io "cluster" not found
                  metadata: {}
                  reason: NotFound
                  status: Failure,
          }
      occurred
      Ginkgo exit error 1: exit with code 1} 

      https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-upi/1758372765364129792

      https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.15-e2e-aws-ovn-upi/1758308563689672704

            mimccune@redhat.com Michael McCune
            stbenjam Stephen Benjamin
            Huali Liu Huali Liu
            Jeana Routh Jeana Routh
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: