Skip to content

opendatahub: Upgrade cluster pool from 4.19 to 4.20#77557

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
dayakar349:upgrade-opendatahub-pool-to-4.20
Apr 8, 2026
Merged

opendatahub: Upgrade cluster pool from 4.19 to 4.20#77557
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
dayakar349:upgrade-opendatahub-pool-to-4.20

Conversation

@dayakar349
Copy link
Copy Markdown
Contributor

@dayakar349 dayakar349 commented Apr 8, 2026

Create new opendatahub-ocp-4-20-amd64-aws cluster pool. This resolves 4.19 cert rotation regression that causes ServiceAccount controller failures after hibernation.

Changes:

  • Add 4.20 cluster pool with size 12, maxSize 40, runningCount 2

@openshift-ci openshift-ci bot requested review from den-rgb and valdar April 8, 2026 17:50
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 8, 2026
@dayakar349
Copy link
Copy Markdown
Contributor Author

/pj-rehearse

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

Add new opendatahub-ocp-4-20-amd64-aws cluster pool to resolve 4.19 cert rotation regression causing ServiceAccount controller failures.

Pool configuration:
- Version: 4.20 (imageSet: ocp-release-4.20.17-multi)
- Size: 12 clusters, maxSize: 40, runningCount: 2
- Region: us-east-1 (AWS)
- Hibernation resume timeout: 20m

This creates the pool but does not switch CI jobs to use it yet. A follow-up
PR will update ci-operator config to use version 4.20 after the pool is ready.
@dayakar349 dayakar349 force-pushed the upgrade-opendatahub-pool-to-4.20 branch from d019f93 to 5ad08b5 Compare April 8, 2026 19:02
@openshift-ci-robot openshift-ci-robot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 8, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

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

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

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.

@dayakar349
Copy link
Copy Markdown
Contributor Author

@carlkyrillos
Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci bot commented Apr 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: carlkyrillos, dayakar349

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

openshift-ci bot commented Apr 8, 2026

@dayakar349: 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/opendatahub-io/opendatahub-operator/main/opendatahub-operator-rhoai-e2e d019f93 link unknown /pj-rehearse pull-ci-opendatahub-io-opendatahub-operator-main-opendatahub-operator-rhoai-e2e
ci/rehearse/opendatahub-io/opendatahub-operator/main/opendatahub-operator-e2e d019f93 link unknown /pj-rehearse pull-ci-opendatahub-io-opendatahub-operator-main-opendatahub-operator-e2e

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 bc43c68 into openshift:main Apr 8, 2026
21 checks passed
@dayakar349 dayakar349 deleted the upgrade-opendatahub-pool-to-4.20 branch April 8, 2026 20:36
dayakar349 pushed a commit to dayakar349/release that referenced this pull request Apr 8, 2026
Update ci-operator config to use version 4.20 clusters now that the pool
exists and is ready (created in PR openshift#77557).

Changes:
- Update releases.latest.version: 4.19 -> 4.20
- Update opendatahub-operator-e2e cluster_claim.version: 4.19 -> 4.20
- Update opendatahub-operator-rhoai-e2e cluster_claim.version: 4.19 -> 4.20

This completes the migration to OCP 4.20, resolving 4.19 cert rotation regression causing SA controller failures.
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. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants