Skip to content

[release-4.22] USHIFT-7169: Add RHEL 10.2 RPM standard release test scenario#6932

Open
agullon wants to merge 1 commit into
openshift:release-4.22from
agullon:USHIFT-7169-release-4.22
Open

[release-4.22] USHIFT-7169: Add RHEL 10.2 RPM standard release test scenario#6932
agullon wants to merge 1 commit into
openshift:release-4.22from
agullon:USHIFT-7169-release-4.22

Conversation

@agullon

@agullon agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Summary

Backport of #6873 to release-4.22.

Add el102@rpm-standard.sh under test/scenarios-bootc/el10/releases/
for testing MicroShift RPM lifecycle on a bare RHEL 10.2 VM.

Adapted configure_rhocp_repo to the release-4.22 2-arg interface
(hardcoded major version 4) since MAJOR_VERSION is not available
on this branch.

Test plan

  • e2e-aws-tests-bootc-release-el10 passes
  • e2e-aws-tests-bootc-release-arm-el10 passes

JIRA: https://issues.redhat.com/browse/USHIFT-7169

Add el102@rpm-standard.sh under test/scenarios-bootc/el10/releases/
for testing MicroShift RPM lifecycle on a bare RHEL 10.2 VM.

Runs install, standard1, standard2, and remove test suites
sequentially on a single VM.

Adapted from el98@rpm-standard{1,2}.sh with RHEL 10 adaptations:
- rhel102-installer VM image
- CDN repo files with entitlement certs for rhocp/fast-datapath
- subscription-manager release set to 10.2

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

pre-commit.check-secrets: ENABLED
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 24, 2026
@openshift-ci-robot

openshift-ci-robot commented Jun 24, 2026

Copy link
Copy Markdown

@agullon: This pull request references USHIFT-7169 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 task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

Backport of #6873 to release-4.22.

Add el102@rpm-standard.sh under test/scenarios-bootc/el10/releases/
for testing MicroShift RPM lifecycle on a bare RHEL 10.2 VM.

Adapted configure_rhocp_repo to the release-4.22 2-arg interface
(hardcoded major version 4) since MAJOR_VERSION is not available
on this branch.

Test plan

  • e2e-aws-tests-bootc-release-el10 passes
  • e2e-aws-tests-bootc-release-arm-el10 passes

JIRA: https://issues.redhat.com/browse/USHIFT-7169

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.

@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

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: 168d6241-85cc-41dc-80a8-e138d442ee39

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.

@openshift-ci openshift-ci Bot requested review from copejon and jerpeter1 June 24, 2026 13:20
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 24, 2026
@agullon

agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

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

@agullon

agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

/retest

@agullon

agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-release-el10
/override ci/prow/e2e-aws-tests-bootc-release-arm-el10

because in both x86 and arm el10 is passing except for the rhel version OS check to 10.2, it says it's 10.1 because for these release is using the cache build images without the updated OS version

@agullon

agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-release-el9
because known bug

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@agullon: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • ci/prow/e2e-aws-tests-bootc-release-el9

Only the following failed contexts/checkruns were expected:

  • CodeRabbit
  • ci/prow/e2e-aws-tests
  • ci/prow/e2e-aws-tests-arm
  • ci/prow/e2e-aws-tests-bootc-arm-el10
  • ci/prow/e2e-aws-tests-bootc-arm-el9
  • ci/prow/e2e-aws-tests-bootc-el10
  • ci/prow/e2e-aws-tests-bootc-el9
  • ci/prow/e2e-aws-tests-bootc-release-arm-el10
  • ci/prow/e2e-aws-tests-bootc-release-el10
  • ci/prow/images
  • ci/prow/security
  • ci/prow/test-unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-microshift-main-e2e-aws-tests
  • pull-ci-openshift-microshift-main-e2e-aws-tests-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm-el10
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm-el9
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-el10
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-el9
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-arm-el10
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-el10
  • pull-ci-openshift-microshift-main-images
  • pull-ci-openshift-microshift-main-security
  • pull-ci-openshift-microshift-main-test-unit
  • pull-ci-openshift-microshift-main-verify
  • pull-ci-openshift-microshift-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-release-el9
because know 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 kubernetes-sigs/prow repository.

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@agullon: Overrode contexts on behalf of agullon: ci/prow/e2e-aws-tests-bootc-release-arm-el10, ci/prow/e2e-aws-tests-bootc-release-el10

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-release-el10
/override ci/prow/e2e-aws-tests-bootc-release-arm-el10

because in both x86 and arm el10 is passing except for the rhel version OS check to 10.2, it says it's 10.1 because for these release is using the cache build images without the updated OS version

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.

@agullon

agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-el9 not related ti this change

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@agullon: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • change
  • not
  • related
  • this
  • ti

Only the following failed contexts/checkruns were expected:

  • CodeRabbit
  • ci/prow/e2e-aws-tests
  • ci/prow/e2e-aws-tests-arm
  • ci/prow/e2e-aws-tests-bootc-arm-el10
  • ci/prow/e2e-aws-tests-bootc-arm-el9
  • ci/prow/e2e-aws-tests-bootc-el10
  • ci/prow/e2e-aws-tests-bootc-el9
  • ci/prow/e2e-aws-tests-bootc-release-arm-el10
  • ci/prow/e2e-aws-tests-bootc-release-el10
  • ci/prow/images
  • ci/prow/security
  • ci/prow/test-unit
  • ci/prow/verify
  • ci/prow/verify-deps
  • pull-ci-openshift-microshift-main-e2e-aws-tests
  • pull-ci-openshift-microshift-main-e2e-aws-tests-arm
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm-el10
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-arm-el9
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-el10
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-el9
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-arm-el10
  • pull-ci-openshift-microshift-main-e2e-aws-tests-bootc-release-el10
  • pull-ci-openshift-microshift-main-images
  • pull-ci-openshift-microshift-main-security
  • pull-ci-openshift-microshift-main-test-unit
  • pull-ci-openshift-microshift-main-verify
  • pull-ci-openshift-microshift-main-verify-deps
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-el9 not related ti this change

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.

@agullon

agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

/override ci/prow/e2e-aws-tests-bootc-el9
not related ti this change

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@agullon: Overrode contexts on behalf of agullon: ci/prow/e2e-aws-tests-bootc-el9

Details

In response to this:

/override ci/prow/e2e-aws-tests-bootc-el9
not related ti this change

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.

@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

@agullon: 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-arm-el10 00b3b86 link true /test e2e-aws-tests-bootc-release-arm-el10
ci/prow/e2e-aws-tests-bootc-el9 00b3b86 link true /test e2e-aws-tests-bootc-el9
ci/prow/e2e-aws-tests-bootc-release-el10 00b3b86 link true /test e2e-aws-tests-bootc-release-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.

@agullon

agullon commented Jun 24, 2026

Copy link
Copy Markdown
Contributor Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jun 24, 2026
@openshift-ci-robot

Copy link
Copy Markdown

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

@ggiguash

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 24, 2026
@openshift-ci

openshift-ci Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

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

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

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.

3 participants