CNTRLPLANE-2123: hypershift: fix version reference from 4.19 to 4.18 by jparrill · Pull Request #72122 · openshift/release

jparrill · 2025-12-03T15:28:11Z

Fix version reference in hypershift release-4.19 configuration.

Updates the version from "4.19" to "4.18" in the initial-418 release section to maintain proper version alignment.

openshift-ci-robot · 2025-12-03T15:28:18Z

@jparrill: This pull request references CNTRLPLANE-2123 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 either version "4.21." or "openshift-4.21.", but it targets "openshift-4.22" instead.

Details

In response to this:

Summary

Bump hypershift CI configuration from OpenShift 4.21 to 4.22

Update base images references to use 4.22 instead of 4.21

Update version references across release configurations (latest, n1minor, n2minor, etc.)

Update test job names and dependencies for version consistency

Remove support for older EOL versions (4.14, 4.18 tests)

Fixes

https://issues.redhat.com/browse/CNTRLPLANE-2123

Test plan

Verify CI job configurations are properly generated

Confirm test jobs execute correctly with new version references

Validate hypershift functionality with 4.22 release images

🤖 Generated with Claude Code

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.

jparrill · 2025-12-03T15:28:34Z

/hold

Until branching happens

bryan-cox · 2025-12-11T13:42:32Z

  steps:
    cluster_profile: hypershift
    dependencies:
      OCP_IMAGE_LATEST: release:latest-420


Why is this not 421, 420, 419, 418, 417?

This is for - as: e2e-aks-4-20, so 4.21 should not be there (?). Regarding others, AKS is not supported under 4.19, even with that, should I put those versions?

sjenning · 2025-12-11T19:41:40Z

+      OCP_IMAGE_LATEST: release:latest-421
+      OCP_IMAGE_N1: release:latest-420
+      OCP_IMAGE_N2: release:latest-419
+      OCP_IMAGE_N3: release:latest-419


should be 418 and then 417

AKS is not supported in versions bellow 4.19, even with that, should I put that value there?

bryan-cox · 2025-12-15T13:20:55Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws

openshift-ci-robot · 2025-12-15T13:20:58Z

@bryan-cox: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

bryan-cox · 2025-12-15T13:21:08Z

/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aks

openshift-ci-robot · 2025-12-15T13:21:11Z

@bryan-cox: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-ci · 2025-12-15T20:52:03Z

@jparrill: 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/rehearse/openshift/hypershift/main/e2e-aws	`b123662`	link	unknown	`/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aws`
ci/rehearse/openshift/hypershift/main/e2e-aks	`b123662`	link	unknown	`/pj-rehearse pull-ci-openshift-hypershift-main-e2e-aks`

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.

sjenning · 2025-12-15T22:44:17Z

      relative: 1
      stream: ci
-      version: "4.19"
+      version: "4.18"


ci-operator/config/openshift-priv is automatically sync'ed from ci-operator/config/openshift on a regular basis. This change is the only one that is really required.

Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

openshift-ci-robot · 2025-12-16T16:51:14Z

@jparrill: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

Summary

Bump hypershift CI configuration from OpenShift 4.21 to 4.22

Update base images references to use 4.22 instead of 4.21

Update version references across release configurations (latest, n1minor, n2minor, etc.)

Update test job names and dependencies for version consistency

Remove support for older EOL versions (4.14, 4.18 tests)

Fixes

https://issues.redhat.com/browse/CNTRLPLANE-2123

Test plan

Verify CI job configurations are properly generated

Confirm test jobs execute correctly with new version references

Validate hypershift functionality with 4.22 release images

🤖 Generated with Claude Code

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-robot · 2025-12-16T16:51:31Z

@jparrill: This pull request references CNTRLPLANE-2123 which is a valid jira issue.

Details

In response to this:

Summary

Bump hypershift CI configuration from OpenShift 4.21 to 4.22

Update base images references to use 4.22 instead of 4.21

Update version references across release configurations (latest, n1minor, n2minor, etc.)

Update test job names and dependencies for version consistency

Remove support for older EOL versions (4.14, 4.18 tests)

Fixes

https://issues.redhat.com/browse/CNTRLPLANE-2123

Test plan

Verify CI job configurations are properly generated

Confirm test jobs execute correctly with new version references

Validate hypershift functionality with 4.22 release images

🤖 Generated with Claude Code

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.

jparrill · 2025-12-16T16:53:51Z

/hold cancel

openshift-ci-robot · 2025-12-16T16:56:06Z

[REHEARSALNOTIFIER]
@jparrill: no rehearsable tests are affected by this change

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

sjenning · 2025-12-16T16:57:32Z

/pj-rehearse pull-ci-openshift-hypershift-release-4.19-e2e-aws-4-18

openshift-ci-robot · 2025-12-16T16:57:35Z

@sjenning: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

sjenning · 2025-12-16T16:57:54Z

/lgtm

openshift-ci-robot · 2025-12-16T17:00:03Z

@sjenning: job(s): pull-ci-openshift-hypershift-release-4.19-e2e-aws-4-18 either don't exist or were not found to be affected, and cannot be rehearsed

openshift-ci · 2025-12-16T17:04:43Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jparrill, sjenning

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:

~~ci-operator/config/openshift/hypershift/OWNERS~~ [jparrill,sjenning]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

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

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 3, 2025

openshift-ci Bot requested review from bear-redhat and danilo-gemoli December 3, 2025 15:28

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 3, 2025

bryan-cox reviewed Dec 11, 2025

View reviewed changes

Comment thread ci-operator/config/openshift/hypershift/openshift-hypershift-main.yaml Outdated

sjenning reviewed Dec 11, 2025

View reviewed changes

jparrill force-pushed the CNTRLPLANE-2123-custom-config-bump-4-21 branch from 45c3b03 to d21f4b5 Compare December 11, 2025 20:24

openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 11, 2025

openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 12, 2025

sjenning mentioned this pull request Dec 13, 2025

CNTRLPLANE-2123: feat: update latest supported version from 4.21 to 4.22 openshift/hypershift#7315

Merged

4 tasks

jparrill force-pushed the CNTRLPLANE-2123-custom-config-bump-4-21 branch from d21f4b5 to b123662 Compare December 15, 2025 08:54

openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Dec 15, 2025

openshift-ci-robot removed the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 15, 2025

jparrill force-pushed the CNTRLPLANE-2123-custom-config-bump-4-21 branch from b123662 to ea078b2 Compare December 15, 2025 20:32

sjenning reviewed Dec 15, 2025

View reviewed changes

hypershift: fix version reference from 4.19 to 4.18

0e82028

Signed-off-by: Juan Manuel Parrilla Madrid <jparrill@redhat.com>

jparrill changed the title ~~CNTRLPLANE-2123: Bump hypershift CI configuration to 4.22~~ hypershift: fix version reference from 4.19 to 4.18 Dec 16, 2025

openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 16, 2025

jparrill changed the title ~~hypershift: fix version reference from 4.19 to 4.18~~ CNTRLPLANE-2123: hypershift: fix version reference from 4.19 to 4.18 Dec 16, 2025

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 16, 2025

jparrill force-pushed the CNTRLPLANE-2123-custom-config-bump-4-21 branch from ea078b2 to 0e82028 Compare December 16, 2025 16:53

openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 16, 2025

openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Dec 16, 2025

openshift-ci Bot assigned sjenning Dec 16, 2025

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Dec 16, 2025

openshift-merge-bot Bot merged commit d0d1176 into openshift:master Dec 16, 2025
13 checks passed

Uh oh!

Conversation

jparrill commented Dec 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Dec 3, 2025 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Fixes

Test plan

Uh oh!

jparrill commented Dec 3, 2025

Uh oh!

bryan-cox Dec 11, 2025

Choose a reason for hiding this comment

Uh oh!

jparrill Dec 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

sjenning Dec 11, 2025

Choose a reason for hiding this comment

Uh oh!

jparrill Dec 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

bryan-cox commented Dec 15, 2025

Uh oh!

openshift-ci-robot commented Dec 15, 2025

Uh oh!

bryan-cox commented Dec 15, 2025

Uh oh!

openshift-ci-robot commented Dec 15, 2025

Uh oh!

openshift-ci Bot commented Dec 15, 2025

Uh oh!

sjenning Dec 15, 2025

Choose a reason for hiding this comment

Uh oh!

openshift-ci-robot commented Dec 16, 2025

Summary

Fixes

Test plan

Uh oh!

openshift-ci-robot commented Dec 16, 2025 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Fixes

Test plan

Uh oh!

jparrill commented Dec 16, 2025

Uh oh!

openshift-ci-robot commented Dec 16, 2025

Uh oh!

sjenning commented Dec 16, 2025

Uh oh!

openshift-ci-robot commented Dec 16, 2025

Uh oh!

sjenning commented Dec 16, 2025

Uh oh!

openshift-ci-robot commented Dec 16, 2025

Uh oh!

openshift-ci Bot commented Dec 16, 2025

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

jparrill commented Dec 3, 2025 •

edited

Loading

openshift-ci-robot commented Dec 3, 2025 •

edited by openshift-ci Bot

Loading

jparrill Dec 11, 2025 •

edited

Loading

jparrill Dec 11, 2025 •

edited

Loading

openshift-ci-robot commented Dec 16, 2025 •

edited by openshift-ci Bot

Loading