Skip to content

test ote panics#74136

Open
miyadav wants to merge 2 commits intoopenshift:mainfrom
miyadav:otetestcpms
Open

test ote panics#74136
miyadav wants to merge 2 commits intoopenshift:mainfrom
miyadav:otetestcpms

Conversation

@miyadav
Copy link
Copy Markdown
Member

@miyadav miyadav commented Jan 29, 2026

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 29, 2026
@miyadav
Copy link
Copy Markdown
Member Author

miyadav commented Jan 29, 2026

/pj-rehearse periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-1of3 periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-2of3 periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-3of3

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci openshift-ci bot requested review from RadekManak and damdo January 29, 2026 17:06
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jan 29, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

@miyadav
Copy link
Copy Markdown
Member Author

miyadav commented Jan 29, 2026

/pj-rehearse

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@miyadav: 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-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-2of3 N/A periodic Periodic changed
periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-3of3 N/A periodic Periodic changed
periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-1of3 N/A periodic Periodic 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.

@miyadav
Copy link
Copy Markdown
Member Author

miyadav commented Jan 30, 2026

/pj-rehearse

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Jan 30, 2026

@miyadav: 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/periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-2of3 8df4f4d link unknown /pj-rehearse periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-2of3
ci/rehearse/periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-3of3 8df4f4d link unknown /pj-rehearse periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-3of3
ci/rehearse/periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-1of3 8df4f4d link unknown /pj-rehearse periodic-ci-openshift-cluster-control-plane-machine-set-operator-release-4.21-e2e-aws-cpmso-1of3

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.

@miyadav
Copy link
Copy Markdown
Member Author

miyadav commented Feb 24, 2026

/payload-job 4.22

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 24, 2026

@miyadav: the repo openshift/release does not contribute to the OpenShift official images, or the base branch is not currently having images promoted

@miyadav
Copy link
Copy Markdown
Member Author

miyadav commented Feb 24, 2026

/testwith periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning openshift/origin#30792 openshift-eng/ci-test-mapping#614

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 24, 2026

@miyadav, testwith: Error processing request. ERROR:

could not determine job runs: requested job is invalid. needs to be formatted like: <org>/<repo>/<branch>/<variant?>/<job>. instead it was: periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 24, 2026

@miyadav, testwith: could not generate prow job. ERROR:

BUG: test 'periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning' not found in injected config

1 similar comment
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Feb 24, 2026

@miyadav, testwith: could not generate prow job. ERROR:

BUG: test 'periodic-ci-openshift-release-main-nightly-4.22-e2e-aws-disruptive-longrunning' not found in injected config

@openshift-bot
Copy link
Copy Markdown
Contributor

Issues in openshift/release go stale after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 15d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 26, 2026
@openshift-bot
Copy link
Copy Markdown
Contributor

Stale issue in openshift/release rot after 15d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 15d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants