To resolve: ose-cluster-kube-descheduler-operator: file does not exist: /mnt/workspace/jenkins/XXX/distgits/containers/ose-cluster-kube-descheduler-operator/manifests/4.5/image-references
Suggestion to verify the bug was to run all the scheduler operator cases to make sure that there is no regression. Ran all the tests present in the file [1] and did not see any issues, so moving the bug to verified state. [1] https://github.com/openshift/cucushift/blob/master/scheduler/operator.feature Payload used to verify the bug : ================================ [ramakasturinarra@dhcp35-60 verification-tests]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-03-172622 True False 23h Cluster version is 4.5.0-0.nightly-2020-05-03-172622
Ignore comment 3 and moving the bug back to ON_QA.
Moving the bug to verified state as i could deploy a descheduler operator of 4.5 version. [ramakasturinarra@dhcp35-60 ocp_files]$ oc get csv NAME DISPLAY VERSION REPLACES PHASE clusterkubedescheduleroperator.4.5.0-202005161517 Kube Descheduler Operator 4.5.0-202005161517 Succeeded [ramakasturinarra@dhcp35-60 ocp_files]$ oc get subscription NAME PACKAGE SOURCE CHANNEL cluster-kube-descheduler-operator cluster-kube-descheduler-operator qe-app-registry 4.5 [ramakasturinarra@dhcp35-60 ocp_files]$ oc get installplan NAME CSV APPROVAL APPROVED install-b97hr clusterkubedescheduleroperator.4.5.0-202005161517 Automatic true [ramakasturinarra@dhcp35-60 ocp_files]$ oc get pods NAME READY STATUS RESTARTS AGE cluster-6dd98b6459-p2gfz 1/1 Running 0 19m descheduler-operator-64d674f84d-8fk79 1/1 Running 0 59m Verified with the payload below: ================================== [ramakasturinarra@dhcp35-60 ocp_files]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-05-17-235851 True False 121m Cluster version is 4.5.0-0.nightly-2020-05-17-235851
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409