OCPBUGS-65623: Remove exception for monitoring OLM Progression condition

[pedjak]

With merge of #30626 we can remove the exception for OLM
monitoring tests.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

@pedjak: This pull request explicitly references no jira issue.

Details

In response to this:

With merge of #30626 we can remove the exception for OLM
monitoring tests.

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.

[pedjak]

/cc @hongkailiu

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pedjak
Once this PR has been reviewed and has the lgtm label, please assign petr-muller for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[openshift-ci]

@pedjak: 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-aws-ovn-serial-1of2	d9c1b80	link	true	/test e2e-aws-ovn-serial-1of2
ci/prow/e2e-gcp-ovn	d9c1b80	link	true	/test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn-ipv6	d9c1b80	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-aws-ovn-fips	d9c1b80	link	true	/test e2e-aws-ovn-fips

Full PR test history. Your PR dashboard.

Details

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.

[jianzhangbjz]

/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

[openshift-ci]

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

• periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b86b5050-023c-11f1-8a25-8b8572ae219a-0

[jianzhangbjz]

/retest-required

[jianzhangbjz]

/retitle OCPBUGS-65623: Remove exception for monitoring OLM Progression condition

[openshift-ci-robot]

@pedjak: This pull request references Jira Issue OCPBUGS-65623, which is invalid:

• expected the bug to target the "4.22.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.

Details

In response to this:

With merge of #30626 we can remove the exception for OLM
monitoring tests.

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.

[jianzhangbjz]

It failed at https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30754-ci-4.22-e2e-aws-upgrade-ovn-single-node/2019240928673271808

time="2026-02-05T04:01:45Z" level=info msg="event interval matches ConnectionErrorDuringSingleNodeAPIServerTargetDown" locator="{Kind map[deployment:cluster-olm-operator hmsg:6dac4b5eb0 namespace:openshift-cluster-olm-operator]}" message="{OperatorStatusChanged  Status for clusteroperator/olm changed: Degraded message changed from \"All is well\" to \"OperatorControllerStaticResourcesDegraded: \\\"/operand-assets/operator-controller/01-namespace-openshift-operator-controller.yaml\\\" (string): Get \\\"[https://172.30.0.1:443/api/v1/namespaces/openshift-operator-controller](https://172.30.0.1/api/v1/namespaces/openshift-operator-controller)\\\": dial tcp 172.30.0.1:443: connect: connection refused\\nOperatorControllerStaticResourcesDegraded: \\\"/operand-assets/operator-controller/02-openshift-operator-controller-networkpolicy-operator-controller-default-deny-all-traffic.yaml\\\" (string): Get \\\"[https://172.30.0.1:443/apis/networking.k8s.io/v1/namespaces/openshift-operator-controller/networkpolicies/operator-controller-default-deny-all-traffic](https://172.30.0.1/apis/networking.k8s.io/v1/namespaces/openshift-operator-controller/networkpolicies/operator-controller-default-deny-all-traffic)\\\": dial tcp 172.30.0.1:443: connect: connection refused\\nOperatorControllerStaticResourcesDegraded:

[jianzhangbjz]

/jira refresh

[openshift-ci-robot]

@jianzhangbjz: This pull request references Jira Issue OCPBUGS-65623, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

Details

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.

[jianzhangbjz]

/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

[openshift-ci]

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

• periodic-ci-openshift-release-master-ci-4.22-e2e-aws-upgrade-ovn-single-node

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/75795c40-026b-11f1-86ae-d8537768c738-0

[jianzhangbjz]

As we discussed on Slack, this #30626 only skips the Patch upgrade(4.21.0->4.21.1). For those failures( periodic-ci-openshift-multiarch-master-nightly-4.22-upgrade-from-nightly-4.21-ocp-ovn-remote-s2s-libvirt-multi-p-p), they're Minor upgrades(4.21.x->4.22.x). If we removed this exception, the test case will fail. So, I'd suggest we keep this exception.

[openshift-ci]

@pedjak: This PR was included in a payload test run from openshift/cluster-olm-operator#173
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.22-upgrade-from-stable-4.21-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9b7f3b60-0380-11f1-90eb-7e61d802a20d-0