OCPBUGS-39026: Remove exception for monitoring operator going degraded during upgrade

[dgoodwin]

We believe this is fixed via https://issues.redhat.com/browse/OCPBUGS-57215

Removing this exception will help us see if the problem is full eliminated in CI not just after upgrade, but also anywhere during.

[openshift-ci-robot]

@dgoodwin: This pull request references Jira Issue OCPBUGS-39026, which is invalid:

• expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

We believe this is fixed via https://issues.redhat.com/browse/OCPBUGS-57215

Removing this exception will help us see if the problem is full eliminated in CI not just after upgrade, but also anywhere during.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[dgoodwin]

/payload-job periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips
/payload-job periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-upgrade
/payload-job periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade
/payload-job periodic-ci-openshift-release-master-nightly-4.20-upgrade-from-stable-4.19-e2e-aws-upgrade-ovn-single-node

[openshift-ci]

@dgoodwin: trigger 4 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.20-e2e-aws-ovn-upgrade-fips
• periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-upgrade
• periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-gcp-ovn-rt-upgrade
• periodic-ci-openshift-release-master-nightly-4.20-upgrade-from-stable-4.19-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/61be4090-67e7-11f0-891a-1fe0430c43aa-0

[stbenjam]

/lgtm
/retest-required

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, stbenjam

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dgoodwin,stbenjam]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dgoodwin]

/hold

Until openshift/cluster-monitoring-operator#2629 is backported, for multi-upgrade jobs

[dgoodwin]

/hold cancel

@wking this is now merged as far back as 4.18 and on it's way to 4.16. Good to go I assume? Re-hold if not!

[wking]

/Jira refresh

[openshift-ci-robot]

@wking: This pull request references Jira Issue OCPBUGS-39026, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/Jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-robot]

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

@dgoodwin: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-vsphere-ovn-etcd-scaling	1910ae0	link	false	/test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-gcp-fips-serial-2of2	1910ae0	link	false	/test e2e-gcp-fips-serial-2of2
ci/prow/e2e-openstack-ovn	1910ae0	link	false	/test e2e-openstack-ovn
ci/prow/e2e-aws-ovn-etcd-scaling	1910ae0	link	false	/test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-ovn-etcd-scaling	1910ae0	link	false	/test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	1910ae0	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-openstack-serial	1910ae0	link	false	/test e2e-openstack-serial
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2	1910ae0	link	false	/test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-azure-ovn-upgrade	1910ae0	link	false	/test e2e-azure-ovn-upgrade
ci/prow/e2e-azure-ovn-etcd-scaling	1910ae0	link	false	/test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-cgroupsv2	1910ae0	link	false	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-gcp-fips-serial-1of2	1910ae0	link	false	/test e2e-gcp-fips-serial-1of2
ci/prow/e2e-aws-ovn-single-node	1910ae0	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-disruptive	1910ae0	link	false	/test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway	1910ae0	link	false	/test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-gcp-disruptive	1910ae0	link	false	/test e2e-gcp-disruptive
ci/prow/e2e-vsphere-ovn	1910ae0	link	true	/test e2e-vsphere-ovn
ci/prow/e2e-gcp-csi	1910ae0	link	true	/test e2e-gcp-csi
ci/prow/e2e-aws-csi	1910ae0	link	true	/test e2e-aws-csi
ci/prow/go-verify-deps	1910ae0	link	true	/test go-verify-deps
ci/prow/e2e-aws-ovn-microshift	1910ae0	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-microshift-serial	1910ae0	link	true	/test e2e-aws-ovn-microshift-serial
ci/prow/e2e-metal-ipi-ovn-ipv6	1910ae0	link	true	/test e2e-metal-ipi-ovn-ipv6

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.