SREP-4345: Skip CSI Mock volume expansion flake in Classic STS conformance

[dustman9000]

Summary

Skip the CSI Mock volume expansion recovery test in the ROSA Classic STS conformance workflow. This is a known upstream flake that fails intermittently across all platforms.

Jira: https://redhat.atlassian.net/browse/SREP-4345

[openshift-ci-robot]

@dustman9000: This pull request references SREP-4345 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

Skip the CSI Mock volume expansion recovery test in the ROSA Classic STS conformance workflow. This is a known upstream flake that fails intermittently across all platforms.

Jira: https://redhat.atlassian.net/browse/SREP-4345

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-ci-robot]

[REHEARSALNOTIFIER]
@dustman9000: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-operator-framework-operator-controller-release-4.22-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-release-main-nightly-4.23-e2e-rosa-sts-ovn	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-operator-controller-release-4.23-periodics-e2e-rosa-sts-ovn-slow-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-release-main-nightly-4.21-e2e-rosa-sts-ovn	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-operator-controller-release-4.21-periodics-e2e-rosa-sts-ovn-slow-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-release-main-nightly-4.18-e2e-rosa-sts-ovn	N/A	periodic	Registry content changed
periodic-ci-openshift-release-main-nightly-4.22-e2e-rosa-sts-ovn	N/A	periodic	Registry content changed
periodic-ci-openshift-release-main-nightly-4.19-e2e-rosa-sts-ovn	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-olm-release-4.22-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-olm-release-4.21-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-olm-release-5.0-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-operator-controller-release-4.23-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-operator-controller-release-5.0-periodics-e2e-rosa-sts-ovn-slow-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-release-main-nightly-4.20-e2e-rosa-sts-ovn	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-olm-release-4.23-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-release-main-nightly-5.0-e2e-rosa-sts-ovn	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-operator-controller-release-4.22-periodics-e2e-rosa-sts-ovn-slow-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-operator-controller-release-5.0-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed
periodic-ci-openshift-operator-framework-operator-controller-release-4.21-periodics-e2e-rosa-sts-ovn-extended-f3	N/A	periodic	Registry content changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[dustman9000]

/pj-rehearse periodic-ci-openshift-release-main-nightly-4.21-e2e-rosa-sts-ovn

[openshift-ci-robot]

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[dustman9000]

/pj-rehearse ack

[openshift-ci-robot]

@dustman9000: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[joshbranham]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustman9000, joshbranham

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/step-registry/rosa/aws/sts/conformance/OWNERS [dustman9000,joshbranham]

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

[openshift-ci]

@dustman9000: 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.