Skip to content

[release-4.19] USHIFT-5584: Revert to using rhel-9.6 base image for ISO generation in CI#5044

Merged
openshift-merge-bot[bot] merged 5 commits intoopenshift:release-4.19from
ggiguash:use_rhel96_419
Jun 12, 2025
Merged

[release-4.19] USHIFT-5584: Revert to using rhel-9.6 base image for ISO generation in CI#5044
openshift-merge-bot[bot] merged 5 commits intoopenshift:release-4.19from
ggiguash:use_rhel96_419

Conversation

@ggiguash
Copy link
Copy Markdown
Contributor

Manual cherry-pick of #5008

P.S. Includes a backport for USHIFT-5464

@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 11, 2025
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jun 11, 2025

@ggiguash: This pull request references USHIFT-5584 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.19.0" version, but no target version was set.

Details

In response to this:

Manual cherry-pick of #5008

P.S. Includes a backport for USHIFT-5464

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 11, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 11, 2025

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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 11, 2025
@ggiguash
Copy link
Copy Markdown
Contributor Author

/test ?

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 11, 2025

@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-cache
/test e2e-aws-tests-cache-arm
/test e2e-aws-tests-periodic
/test e2e-aws-tests-periodic-arm
/test images
/test ocp-full-conformance-rhel-eus
/test ocp-full-conformance-serial-rhel-eus
/test test-rpm
/test test-unit
/test verify

The following commands are available to trigger optional jobs:

/test security
/test test-rebase

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

pull-ci-openshift-microshift-release-4.19-e2e-aws-tests
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-arm
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc-arm
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc-periodic
pull-ci-openshift-microshift-release-4.19-e2e-aws-tests-bootc-periodic-arm
pull-ci-openshift-microshift-release-4.19-images
pull-ci-openshift-microshift-release-4.19-security
pull-ci-openshift-microshift-release-4.19-test-unit
pull-ci-openshift-microshift-release-4.19-verify
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
Copy Markdown
Contributor Author

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

@ggiguash
Copy link
Copy Markdown
Contributor Author

ggiguash commented Jun 11, 2025

Brew RPM download timed out

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

1 similar comment
@ggiguash
Copy link
Copy Markdown
Contributor Author

Brew RPM download timed out

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

@ggiguash ggiguash marked this pull request as ready for review June 11, 2025 16:20
@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 Jun 11, 2025
@openshift-ci openshift-ci Bot requested review from jerpeter1 and vanhalenar June 11, 2025 16:20
@ggiguash
Copy link
Copy Markdown
Contributor Author

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

@ggiguash
Copy link
Copy Markdown
Contributor Author

/test all

@ggiguash
Copy link
Copy Markdown
Contributor Author

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

@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 Jun 12, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 12, 2025

@ggiguash: The label(s) /label cherrypick-approved cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

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

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

/label cherry-pick-approved

@openshift-ci openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 12, 2025
@ggiguash
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-bootc-periodic

@pmtk
Copy link
Copy Markdown
Member

pmtk commented Jun 12, 2025

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 12, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@ggiguash
Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-bootc-periodic

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 12, 2025

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

@openshift-merge-bot openshift-merge-bot Bot merged commit ba6ea77 into openshift:release-4.19 Jun 12, 2025
13 checks passed
@ggiguash ggiguash deleted the use_rhel96_419 branch June 12, 2025 14:32
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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants