Skip to content

[release-4.22] USHIFT-6887: Fix microshift-low-latency for RHEL10#6614

Open
openshift-cherrypick-robot wants to merge 3 commits intoopenshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-6590-to-release-4.22
Open

[release-4.22] USHIFT-6887: Fix microshift-low-latency for RHEL10#6614
openshift-cherrypick-robot wants to merge 3 commits intoopenshift:release-4.22from
openshift-cherrypick-robot:cherry-pick-6590-to-release-4.22

Conversation

@openshift-cherrypick-robot
Copy link
Copy Markdown

@openshift-cherrypick-robot openshift-cherrypick-robot commented Apr 30, 2026

This is an automated cherry-pick of #6590

/assign agullon

pmtk added 3 commits April 30, 2026 10:29
@pmtk
microshift-low-latency for RHEL10
a4746d8 
RHEL10 uses different path for the profiles, so while we're still using
RHEL9 for the builders, we need a workaround to make the package usage
on both systems
@pmtk
low latency periodics
3ce69ca
@pmtk
WP: Wait for MicroShift
e37cb51
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Apr 30, 2026
Merged
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 30, 2026 •
edited by openshift-ci Bot
Loading

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

Details

In response to this:

This is an automated cherry-pick of #6590

/assign agullon

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 requested review from eslutsky and jogeo April 30, 2026 10:30
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 30, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 0719cfba-6917-44c5-b113-f59e1d7f3d0d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@agullon
Copy link
Copy Markdown
Contributor

agullon commented Apr 30, 2026

/label jira/valid-bug
/label backport-risk-assessed
/lgtm
/verified by CI

@openshift-ci openshift-ci Bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Apr 30, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 30, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Apr 30, 2026

@agullon: This PR has been marked as verified by CI.

Details

In response to this:

/label jira/valid-bug
/label backport-risk-assessed
/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 Apr 30, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 30, 2026

[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 Apr 30, 2026
@agullon
Copy link
Copy Markdown
Contributor

agullon commented Apr 30, 2026

/test e2e-aws-tests-release
/test e2e-aws-tests-release-arm
/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10
/test e2e-aws-tests-bootc-release-arm-el9
/test e2e-aws-tests-bootc-release-arm-el10

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

openshift-merge-bot Bot commented Apr 30, 2026

/retest-required

Remaining retests: 0 against base HEAD 0166e53 and 2 for PR HEAD e37cb51 in total

@agullon
Copy link
Copy Markdown
Contributor

agullon commented Apr 30, 2026

/retest

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

openshift-merge-bot Bot commented Apr 30, 2026

/retest-required

Remaining retests: 0 against base HEAD b4429ec and 1 for PR HEAD e37cb51 in total

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

openshift-merge-bot Bot commented May 1, 2026

/retest-required

Remaining retests: 0 against base HEAD d61265c and 0 for PR HEAD e37cb51 in total

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

@openshift-cherrypick-robot: 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/prow/e2e-aws-tests-bootc-release-el10 e37cb51 link true /test e2e-aws-tests-bootc-release-el10
ci/prow/e2e-aws-tests-bootc-release-arm-el10 e37cb51 link true /test e2e-aws-tests-bootc-release-arm-el10

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
Copy link
Copy Markdown
Contributor

openshift-merge-bot Bot commented May 1, 2026

/hold

Revision e37cb51 was retested 3 times: holding

@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 May 1, 2026
@agullon
Copy link
Copy Markdown
Contributor

agullon commented May 3, 2026

/test e2e-aws-tests-cache
/test e2e-aws-tests-cache-arm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@eslutsky eslutsky Awaiting requested review from eslutsky

@jogeo jogeo Awaiting requested review from jogeo

Assignees

@agullon agullon

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@openshift-cherrypick-robot @openshift-ci-robot @agullon @pmtk