Skip to content

NO-ISSUE: rebase-main-4.20.0-0.nightly-2025-07-01-051543_amd64-2025-07-01_arm64-2025-07-03 #5137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 5 commits into from
Jul 4, 2025
Merged

NO-ISSUE: rebase-main-4.20.0-0.nightly-2025-07-01-051543_amd64-2025-07-01_arm64-2025-07-03 #5137

merged 5 commits into from
Jul 4, 2025

Conversation

microshift-rebase-script[bot]
Copy link
Contributor

amd64: 4.20.0-0.nightly-2025-07-01-051543
arm64: 4.20.0-0.nightly-arm64-2025-07-03-211005
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1940984097035784192

  • oc image-arm64 ea5c72052233361761ba371b7c39518d443422be to f0e10516c2bab32e797240b7bd4a2c6563138709
    • 83321f44 2025-07-02T21:44:54+05:30 Introduce a dedicated Pod label for the purpose of identifying debug pods

/label tide/merge-method-squash
/label cherry-pick-approved
/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 Jul 4, 2025
@openshift-ci-robot
Copy link

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

In response to this:

amd64: 4.20.0-0.nightly-2025-07-01-051543
arm64: 4.20.0-0.nightly-arm64-2025-07-03-211005
prow job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-microshift-main-rebase-on-nightlies/1940984097035784192

  • oc image-arm64 ea5c72052233361761ba371b7c39518d443422be to f0e10516c2bab32e797240b7bd4a2c6563138709
  • 83321f44 2025-07-02T21:44:54+05:30 Introduce a dedicated Pod label for the purpose of identifying debug pods

/label tide/merge-method-squash
/label cherry-pick-approved
/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 tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. labels Jul 4, 2025
@microshift-rebase-script microshift-rebase-script
Copy link
Contributor Author

Extra messages:

  • Deleted following branches: rebase-release-4.16-4.16.0-0.nightly-2025-07-01-031707_amd64-2025-07-01_arm64-2025-07-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 Jul 4, 2025
@openshift-ci openshift-ci bot requested review from agullon and eslutsky July 4, 2025 04:23
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 4, 2025

@microshift-rebase-script[bot]: all tests passed!

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 Jul 4, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 4, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 4, 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 Jul 4, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 35835f0 into main Jul 4, 2025
13 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the rebase-main-4.20.0-0.nightly-2025-07-01-051543_amd64-2025-07-01_arm64-2025-07-03 branch July 4, 2025 07:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@agullon agullon Awaiting requested review from agullon

@eslutsky eslutsky Awaiting requested review from eslutsky

Assignees

@pmtk pmtk

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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@openshift-ci-robot @pmtk