Skip to content

[release-4.22] NO-ISSUE: Update common_versions.sh#6984

Merged
openshift-merge-bot[bot] merged 1 commit into
release-4.22from
common-versions-update-release-4.22
Jul 4, 2026
Merged

[release-4.22] NO-ISSUE: Update common_versions.sh#6984
openshift-merge-bot[bot] merged 1 commit into
release-4.22from
common-versions-update-release-4.22

Conversation

@microshift-rebase-script

Copy link
Copy Markdown
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 3, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@microshift-rebase-script[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

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 agullon and jerpeter1 July 3, 2026 14:42
@microshift-rebase-script

Copy link
Copy Markdown
Contributor Author

/test e2e-aws-tests-bootc-el10

Added by prow-jobs-for-pull-requests.sh 🤖

@ggiguash

ggiguash commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci Bot commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, microshift-rebase-script[bot]

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 Jul 4, 2026
@ggiguash

ggiguash commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

The problem is that we're still using EL10 images from OCP mirror cache. Not related to this PR - will be fixed in a follow-up PR.

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

@openshift-ci

openshift-ci Bot commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

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

Details

In response to this:

The problem is that we're still using EL10 images from OCP mirror cache. Not related to this PR - will be fixed in a follow-up PR.

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

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 Jul 4, 2026

Copy link
Copy Markdown
Contributor

@microshift-rebase-script[bot]: 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-arm-el10 4656c3e link true /test e2e-aws-tests-bootc-arm-el10
ci/prow/e2e-aws-tests-bootc-el10 4656c3e link true /test e2e-aws-tests-bootc-el10
ci/prow/e2e-aws-tests-bootc-periodic-arm-el10 4656c3e link true /test e2e-aws-tests-bootc-periodic-arm-el10
ci/prow/e2e-aws-tests-bootc-periodic-el10 4656c3e link true /test e2e-aws-tests-bootc-periodic-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.

@ggiguash

ggiguash commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

/label jira/valid-bug
/label backport-risk-assessed
/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 Jul 4, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jul 4, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@ggiguash: This PR has been marked as verified by ci.

Details

In response to this:

/label jira/valid-bug
/label backport-risk-assessed
/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 c9b015f into release-4.22 Jul 4, 2026
18 checks passed
@openshift-merge-bot openshift-merge-bot Bot deleted the common-versions-update-release-4.22 branch July 4, 2026 05:48
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. 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

Development

Successfully merging this pull request may close these issues.

2 participants