Skip to content

Conversation

@microshift-rebase-script
Copy link
Contributor

amd64: 4.21.0-0.nightly-2025-11-22-193140
arm64: 4.21.0-0.nightly-arm64-2025-12-02-002806
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.21-periodics-rebase-on-nightlies/1995704866617430016

  • oc image-arm64 02aba637a54c5d1317b5c284e213d7a85d64d6bb to fceda801d53976068ddc56ac642c7fd4bd47f5de

    • 232df150 2025-12-01T13:39:19+01:00 .claude: Improve pr-review command/skill
  • kubernetes image-arm64 f6c89d1c3286d2f58dff24c38cbb0eaedab00c4c to e98e941a29558dd88e3a0df1c132d2968b5de793

    • ce2ef9665 2025-11-26T13:47:28-08:00 UPSTREAM: : move disabled HPA tests from Broken to DedicatedJob
    • d3c4628d8 2025-10-24T07:15:08-04:00 UPSTREAM: : Remove duplicate VolumeGroupSnapshottableTestSuite from CSISuites

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 2, 2025
@openshift-ci-robot
Copy link

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

In response to this:

amd64: 4.21.0-0.nightly-2025-11-22-193140
arm64: 4.21.0-0.nightly-arm64-2025-12-02-002806
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-release-4.21-periodics-rebase-on-nightlies/1995704866617430016

  • oc image-arm64 02aba637a54c5d1317b5c284e213d7a85d64d6bb to fceda801d53976068ddc56ac642c7fd4bd47f5de

  • 232df150 2025-12-01T13:39:19+01:00 .claude: Improve pr-review command/skill

  • kubernetes image-arm64 f6c89d1c3286d2f58dff24c38cbb0eaedab00c4c to e98e941a29558dd88e3a0df1c132d2968b5de793

  • ce2ef9665 2025-11-26T13:47:28-08:00 UPSTREAM: : move disabled HPA tests from Broken to DedicatedJob

  • d3c4628d8 2025-10-24T07:15:08-04:00 UPSTREAM: : Remove duplicate VolumeGroupSnapshottableTestSuite from CSISuites

/label tide/merge-method-squash
/label backport-risk-assessed
/label jira/valid-bug

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 openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Dec 2, 2025
@microshift-rebase-script
Copy link
Contributor Author

Extra messages:

  • Deleted following branches: rebase-master-4.21.0-0.nightly-2025-11-22-193140_amd64-2025-11-22_arm64-2025-12-01

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Dec 2, 2025
@openshift-ci openshift-ci bot requested review from copejon and vanhalenar December 2, 2025 04:14
@pmtk
Copy link
Member

pmtk commented Dec 2, 2025

/retest

2 similar comments
@pmtk
Copy link
Member

pmtk commented Dec 2, 2025

/retest

@pmtk
Copy link
Member

pmtk commented Dec 3, 2025

/retest

@pmtk
Copy link
Member

pmtk commented Dec 3, 2025

/lgtm
/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 3, 2025
@openshift-ci-robot
Copy link

@pmtk: This PR has been marked as verified by ci.

In response to this:

/lgtm
/verified by ci

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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: microshift-rebase-script[bot], pmtk

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

The pull request process is described here

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 3, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD ae559a2 and 2 for PR HEAD 75ad247 in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD e956e17 and 1 for PR HEAD 75ad247 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

@microshift-rebase-script: The following test 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-tests-bootc-arm 75ad247 link unknown /test e2e-aws-tests-bootc-arm

Full PR test history. Your PR dashboard.

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.

@pmtk
Copy link
Member

pmtk commented Dec 4, 2025

/close

@openshift-ci openshift-ci bot closed this Dec 4, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 4, 2025

@pmtk: Closed this PR.

In response to this:

/close

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.

@microshift-rebase-script microshift-rebase-script bot deleted the rebase-release-4.21-4.21.0-0.nightly-2025-11-22-193140_amd64-2025-11-22_arm64-2025-12-02 branch December 5, 2025 04:20
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants