Move oc-adm-upgrade-status and audit-log-analyzer to default

[sergiordlr]

Move oc-adm-upgrade-status monitoring test to default, so that it is not run when executing disruptive test suites.

Add exceptions for MCO in audit-log-analyzer, since MCO tests last 23 hours and it is normal to exceed the limit.

• oc-adm-upgrade-status cannot get the necessary information when the cluster is not able to answer, and it fails. (We see it especially when the tests change the TLS configuration in the apiserver "cluster" resource.

oc adm upgrade status failed 2 times (of 723)  - 2026-02-04T20:02:55Z: failed to run oc adm upgrade status after 2 attempts: context deadline exceeded
recorded attempts and outputs:
Attempt #1 failed: Error running oc --kubeconfig=/tmp/kubeconfig-681483446 adm upgrade status --details=all:
StdOut>
Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get clusterversions.config.openshift.io version)

• audit-log-analyzer: MCO is considered as flake

                                    "system:serviceaccount:openshift-machine-config-operator:machine-config-daemon"
                                    "system:serviceaccount:openshift-machine-config-operator:machine-config-controller

[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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sergiordlr
Once this PR has been reviewed and has the lgtm label, please assign stbenjam 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-trt]

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: 8bbde96

• "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vmware-vsphere-csi-driver-operator should not create excessive watch requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
• "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vsphere-problem-detector-operator should not create excessive watch requests" [Total: 2, Pass: 2, Fail: 0, Flake: 0]

[sergiordlr]

/test e2e-aws-csi
/test e2e-metal-ipi-ovn-ipv6
/test e2e-aws-ovn-microshift

[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

[sergiordlr]

/test e2e-gcp-ovn
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial

[openshift-ci]

@sergiordlr: all tests passed!

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.