Skip to content

[release-4.20] USHIFT-6161: Add bootc files related to low-latency#5580

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
openshift-cherrypick-robot:cherry-pick-5565-to-release-4.20
Oct 13, 2025
Merged

[release-4.20] USHIFT-6161: Add bootc files related to low-latency#5580
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.20from
openshift-cherrypick-robot:cherry-pick-5565-to-release-4.20

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #5565

/assign kasturinarra

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 8, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-6161

Details

In response to this:

This is an automated cherry-pick of #5565

/assign kasturinarra

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.

@kasturinarra
Copy link
Contributor

@agullon could you please help review and merge ? thanks !!

@agullon
Copy link
Contributor

agullon commented Oct 9, 2025

/lgtm

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

openshift-ci bot commented Oct 9, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, openshift-cherrypick-robot

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

/verified by ci

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

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

Details

In response to this:

/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.

@jerpeter1
Copy link
Member

/label staff-eng-approved

@openshift-ci openshift-ci bot added the staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). label Oct 10, 2025
@ggiguash
Copy link
Contributor

/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Oct 10, 2025
@ggiguash
Copy link
Contributor

/label backport-risk-assessed

@ggiguash
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Oct 13, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

@openshift-cherrypick-robot: 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.

@openshift-merge-bot openshift-merge-bot bot merged commit d913e53 into openshift:release-4.20 Oct 13, 2025
13 checks passed
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. lgtm Indicates that a PR is ready to be merged. staff-eng-approved Indicates a release branch PR has been approved by a staff engineer (formerly group/pillar lead). verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants