Skip to content

USHIFT-6161: Add bootc files related to low-latency#5565

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kasturinarra:USHIFT-6161
Oct 8, 2025
Merged

USHIFT-6161: Add bootc files related to low-latency#5565
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
kasturinarra:USHIFT-6161

Conversation

@kasturinarra
Copy link
Contributor

@kasturinarra kasturinarra commented Oct 6, 2025

Which issue(s) this PR addresses: Addresses adding low-latency profile for bootc

Closes #USHIFT-6161

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

openshift-ci-robot commented Oct 6, 2025

@kasturinarra: This pull request references USHIFT-6161 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses: Addresses adding low-latency profile for bootc

Closes #USHIFT-6161

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.

1 similar comment
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 6, 2025

@kasturinarra: This pull request references USHIFT-6161 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.21.0" version, but no target version was set.

Details

In response to this:

Which issue(s) this PR addresses: Addresses adding low-latency profile for bootc

Closes #USHIFT-6161

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 Author

@agullon could you please help review ? thanks !!

@openshift-ci openshift-ci bot requested review from pacevedom and vanhalenar October 6, 2025 17:41
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 6, 2025
@agullon
Copy link
Contributor

agullon commented Oct 7, 2025

probably I'm missing, why you only add it to bootc but not rpm-ostree?

@kasturinarra
Copy link
Contributor Author

/test e2e-aws-tests-arm

@kasturinarra kasturinarra force-pushed the USHIFT-6161 branch 2 times, most recently from f564afc to d70e2f5 Compare October 7, 2025 16:30
@kasturinarra kasturinarra marked this pull request as draft October 7, 2025 16:31
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 7, 2025
@kasturinarra
Copy link
Contributor Author

/test e2e-aws-tests-bootc

@kasturinarra kasturinarra marked this pull request as ready for review October 8, 2025 06:32
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 8, 2025
@openshift-ci openshift-ci bot requested a review from ggiguash October 8, 2025 06:33
@kasturinarra
Copy link
Contributor Author

/test e2e-aws-tests-bootc-arm

@kasturinarra
Copy link
Contributor Author

@agullon could you please help review again ? all tests passed.

@agullon
Copy link
Contributor

agullon commented Oct 8, 2025

/lgtm

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

openshift-ci bot commented Oct 8, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: agullon, kasturinarra

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:
  • OWNERS [agullon,kasturinarra]

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

@kasturinarra
Copy link
Contributor Author

/verified by ci

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 8, 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.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 8, 2025

@kasturinarra: 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 f59cfe9 into openshift:main Oct 8, 2025
13 checks passed
@kasturinarra
Copy link
Contributor Author

/cherry-pick release-4.20

@openshift-cherrypick-robot

@kasturinarra: new pull request created: #5580

Details

In response to this:

/cherry-pick release-4.20

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.

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants