test: operator conditions monitoring is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=operator+conditions+monitoring 4.4.z install on oVirt can't complete as monitoring can't rollout. This blocks 4.4.z -> 4.5 upgrade tests. example job: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/1369211579001737216 level=info msg="Cluster operator monitoring Available is False with : " level=info msg="Cluster operator monitoring Progressing is True with RollOutInProgress: Rolling out the stack." level=error msg="Cluster operator monitoring Degraded is True with UpdatingPrometheusK8SFailed: Failed to rollout the stack. Error: running task Updating Prometheus-k8s failed: waiting for Prometheus object changes failed: waiting for Prometheus: expected 2 replicas, updated 0 and available 0" level=fatal msg="failed to initialize the cluster: Cluster operator monitoring is still updating"
Also happens on 4.5 - https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.6-upgrade-from-stable-4.5-e2e-ovirt-upgrade/1369166292912705536 Seems resolved in 4.8/4.7/4.6
This is a CI only issue and is in progress due to capacity constraints we will be revisiting this bug in the upcoming sprint
Should be the same problem as 4.5 jobs. Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1936857#c5 Moving to Gal.
Not yet fixed - see https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade * https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/1386606443997696000 * https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/1386244053321912320 * https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/1385881662205726720
Hi(In reply to Vadim Rutkovsky from comment #5) > Not yet fixed - see > https://prow.ci.openshift.org/job-history/gs/origin-ci-test/logs/periodic-ci- > openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade > * > https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci- > openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/ > 1386606443997696000 > * > https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci- > openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/ > 1386244053321912320 > * > https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci- > openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/ > 1385881662205726720 Hi those are upgrade jobs and that is a different workflow. I believe that the upgrade issue was resolved by https://github.com/openshift/release/pull/18091. But anyway I think you can mark it as verified since 4.4 jobs are passing installation (hitting docker rate limiting on test cases but that is a different problem)
Moving to verified now
>Hi those are upgrade jobs and that is a different workflow. This is a 4.4 -> 4.5 upgrade job and it still fails: * https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/1394940974563594240 * https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/1394578900389990400 * https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.5-upgrade-from-stable-4.4-e2e-ovirt-upgrade/1394216508506247168 If it needs to use a different workflow please update release configuration
Although, lets create a new issue for that
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 (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), 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/RHSA-2021:2438