Skip to content

[release-4.20] USHIFT-6442: Introduce RPM repository configuration script #6095

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
openshift-merge-bot merged 4 commits into from
Jan 16, 2026
Merged

[release-4.20] USHIFT-6442: Introduce RPM repository configuration script #6095

openshift-merge-bot merged 4 commits into from
Jan 16, 2026

Conversation

@ggiguash
Copy link
Contributor

@ggiguash ggiguash commented Jan 16, 2026

Manual cherry-pick of #6092, including enabling EUS repositories for RHEL 9.4 too.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 16, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 16, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 16, 2026 •
edited by openshift-ci bot
Loading

@ggiguash: This pull request references USHIFT-6442 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 story to target the "4.20.z" version, but no target version was set.

Details

In response to this:

Manual cherry-pick of #6092, including enabling EUS repositories for RHEL 9.4 too.

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jan 16, 2026
@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 16, 2026

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 16, 2026

@ggiguash: The following commands are available to trigger required jobs:

/test e2e-aws-ai-model-serving

/test e2e-aws-footprint-and-performance

/test e2e-aws-tests

/test e2e-aws-tests-arm

/test e2e-aws-tests-bootc

/test e2e-aws-tests-bootc-arm

/test e2e-aws-tests-bootc-periodic

/test e2e-aws-tests-bootc-periodic-arm

/test e2e-aws-tests-bootc-release

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

/test e2e-aws-tests-cache

/test e2e-aws-tests-cache-arm

/test e2e-aws-tests-periodic

/test e2e-aws-tests-periodic-arm

/test e2e-aws-tests-release

/test e2e-aws-tests-release-arm

/test ocp-full-conformance-rhel-eus

/test ocp-full-conformance-serial-rhel-eus

/test test-rpm

/test test-unit

/test verify

/test verify-deps

The following commands are available to trigger optional jobs:

/test images

/test security

/test test-rebase

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-arm

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-bootc

pull-ci-openshift-microshift-release-4.20-e2e-aws-tests-bootc-arm

pull-ci-openshift-microshift-release-4.20-images

pull-ci-openshift-microshift-release-4.20-security

pull-ci-openshift-microshift-release-4.20-test-unit

pull-ci-openshift-microshift-release-4.20-verify

pull-ci-openshift-microshift-release-4.20-verify-deps
Details

In response to this:

/test ?

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.

@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 16, 2026

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

@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 16, 2026

/test e2e-aws-tests-cache

@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 16, 2026

/test e2e-aws-tests-cache-arm

@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 16, 2026

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

@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 16, 2026

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

@ggiguash ggiguash marked this pull request as ready for review January 16, 2026 16:12
@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 Jan 16, 2026
@openshift-ci openshift-ci bot requested review from eslutsky and vanhalenar January 16, 2026 16:12
@ggiguash
Copy link
Contributor Author

ggiguash commented Jan 16, 2026

/test all

@pacevedom
Copy link
Contributor

pacevedom commented Jan 16, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 16, 2026

@ggiguash: 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.

@pacevedom
Copy link
Contributor

pacevedom commented Jan 16, 2026

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

@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 Jan 16, 2026
pacevedom
pacevedom approved these changes Jan 16, 2026
View reviewed changes
Copy link
Contributor

@pacevedom pacevedom left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/verified by CI

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 16, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom

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

@pacevedom
Copy link
Contributor

pacevedom commented Jan 16, 2026

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jan 16, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jan 16, 2026

@pacevedom: 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-merge-bot openshift-merge-bot bot merged commit cc344cc into openshift:release-4.20 Jan 16, 2026
12 checks passed
@ggiguash ggiguash deleted the bootc-eus-repos-420 branch January 17, 2026 07:13
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

@vanhalenar vanhalenar Awaiting requested review from vanhalenar

1 more reviewer

@pacevedom pacevedom pacevedom approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

@pacevedom pacevedom

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

3 participants

@ggiguash @openshift-ci-robot @pacevedom