Skip to content

NO-JIRA: Set hypershift-e2e-aks test jobs as optional#76133

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
mpatlasov:NO-JIRA-Set-hypershift-e2e-aks-test-jobs-as-optional
Mar 13, 2026
Merged

NO-JIRA: Set hypershift-e2e-aks test jobs as optional#76133
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
mpatlasov:NO-JIRA-Set-hypershift-e2e-aks-test-jobs-as-optional

Conversation

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 12, 2026
@openshift-ci-robot
Copy link
Contributor

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

Details

In response to this:

This test is perma-faling these days, it doesn't give us any useful signals, see how it failed in the following PRs:

/cc @openshift/storage

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
Copy link
Contributor

openshift-ci bot commented Mar 12, 2026

@mpatlasov: GitHub didn't allow me to request PR reviews from the following users: openshift/storage.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

This test is perma-faling these days, it doesn't give us any useful signals, see how it failed in the following PRs:

/cc @openshift/storage

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 12, 2026
@mpatlasov mpatlasov force-pushed the NO-JIRA-Set-hypershift-e2e-aks-test-jobs-as-optional branch from 73a9167 to 37f8b1a Compare March 12, 2026 20:17
@openshift-ci-robot
Copy link
Contributor

[REHEARSALNOTIFIER]
@mpatlasov: 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
pull-ci-openshift-cluster-storage-operator-main-hypershift-e2e-aks openshift/cluster-storage-operator presubmit Ci-operator config changed
pull-ci-openshift-csi-operator-main-hypershift-e2e-aks openshift/csi-operator presubmit Ci-operator config changed
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.

@mpatlasov
Copy link
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Contributor

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

@mpatlasov
Copy link
Contributor Author

/pj-rehearse ack

CI jobs for hypershift-e2e-aks failed -- that's expected, this test is prema-failing these days. That's exactly why this PR adds "optional" to job definitions.

@openshift-ci-robot
Copy link
Contributor

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

@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Mar 12, 2026
@duanwei33
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: duanwei33, mpatlasov

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:

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

@mpatlasov: 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/rehearse/openshift/csi-operator/main/hypershift-e2e-aks 37f8b1a link unknown /pj-rehearse pull-ci-openshift-csi-operator-main-hypershift-e2e-aks
ci/rehearse/openshift/cluster-storage-operator/main/hypershift-e2e-aks 37f8b1a link unknown /pj-rehearse pull-ci-openshift-cluster-storage-operator-main-hypershift-e2e-aks

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.

@openshift-merge-bot openshift-merge-bot bot merged commit 6d0aa36 into openshift:main Mar 13, 2026
15 of 17 checks passed
qiliRedHat pushed a commit to qiliRedHat/release that referenced this pull request Mar 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants