[release-4.22] MULTIARCH-6077: PowerVS: Fix supported system types retrieval

[taliandre49]

Backport of #10268 to release-22.

This PR fixes supported system type retrieval for PowerVS regions by adding
dal14 region support and enabling the s1122 system type.

Included changes

• pkg/types/powervs: add dal14 region support with s1122
• cluster-api/providers/ibmcloud: bump powervs-utils for s1122 support
• cluster-api/providers/ibmcloud: vendor updated powervs-utils

The powervs-utils version used matches the original change merged to main
and represents the minimal dependency update required for this fix.

Original PR: #10268
Jira: MULTIARCH-5824

[coderabbitai]

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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 535bdf5c-0dc0-42f8-9e87-f30b800f4022

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

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[taliandre49]

status: reviewing failed test

[taliandre49]

/test e2e-ibmcloud-ovn

[sadasu]

/test e2e-ibmcloud-ovn

[sadasu]

/label backport-risk-assessed

[sadasu]

@taliandre49 You'll need a Jira bug just for the backport to 4.22. This bug should depend on MULTIARCH-5824 that already merged.

[taliandre49]

/test e2e-ibmcloud-ovn

[taliandre49]

Status: The failing test appears to be unrelated to the PowerVS dal14 zone updates in this PR. The test is failing due to ingress/networking timeouts during IBM Cloud VPC cluster initialization, not PowerVS configuration issues.

Evidence:

• The test failure occurs in the e2e-ibmcloud-ovn job, which tests IBM Cloud VPC
• This PR only modifies PowerVS zone definitions and system types for dal14, which are not used by this job.
• The failure manifests as:
  • OAuth server route endpoint timeouts
  • Console route health check failures
  • Ingress controller canary check failures (repeated 41 times over 40 minutes)
• The observed failures (OAuth route timeouts, console route health check failures, ingress canary check failures) indicate ingress/network reachability issues during IBM Cloud VPC cluster initialization.

The PowerVS-specific changes in this PR are isolated and should not affect IBM Cloud VPC networking.

[mjturek]

/retitle [release-4.22] OCPBUGS-84875: PowerVS: Fix supported system types retrieval

[openshift-ci-robot]

@taliandre49: This pull request references Jira Issue OCPBUGS-84875, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• dependent bug MULTIARCH-5824 is not in the required OCPBUGS project

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Backport of #10268 to release-22.

This PR fixes supported system type retrieval for PowerVS regions by adding
dal14 region support and enabling the s1122 system type.

Included changes

• pkg/types/powervs: add dal14 region support with s1122
• cluster-api/providers/ibmcloud: bump powervs-utils for s1122 support
• cluster-api/providers/ibmcloud: vendor updated powervs-utils

The powervs-utils version used matches the original change merged to main
and represents the minimal dependency update required for this fix.

Original PR: #10268
Jira: MULTIARCH-5824

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.

[mjturek]

/jira-refresh

[mjturek]

/retitle [release-4.22] MULTIARCH-6077: PowerVS: Fix supported system types retrieval

[openshift-ci-robot]

@taliandre49: This pull request references MULTIARCH-6077 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 bug to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Backport of #10268 to release-22.

This PR fixes supported system type retrieval for PowerVS regions by adding
dal14 region support and enabling the s1122 system type.

Included changes

• pkg/types/powervs: add dal14 region support with s1122
• cluster-api/providers/ibmcloud: bump powervs-utils for s1122 support
• cluster-api/providers/ibmcloud: vendor updated powervs-utils

The powervs-utils version used matches the original change merged to main
and represents the minimal dependency update required for this fix.

Original PR: #10268
Jira: MULTIARCH-5824

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.

[mjturek]

/jira refresh

[openshift-ci-robot]

@mjturek: This pull request references MULTIARCH-6077 which is a valid jira issue.

Details

In response to this:

/jira refresh

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.

[taliandre49]

/test govet

[taliandre49]

/test e2e-ibmcloud-ovn

[mjturek]

/lgtm

[mjturek]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: mjturek
Once this PR has been reviewed and has the lgtm label, please assign rvanderp3 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• cluster-api/providers/ibmcloud/OWNERS
• pkg/asset/installconfig/powervs/OWNERS [mjturek]
• pkg/types/powervs/OWNERS [mjturek]

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

[mjturek]

/assign bobbyradford

[openshift-ci]

@mjturek: GitHub didn't allow me to assign the following users: bobbyradford.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign bobbyradford

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.

[mjturek]

/assign hasueki

[openshift-ci]

@mjturek: GitHub didn't allow me to assign the following users: hasueki.

Note that only openshift members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign hasueki

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.

[mjturek]

/assign rvanderp3

[rvanderp3]

/unassign

[rvanderp3]

/unassign

I'm not familiar enough with the changes to confidently approve. @patrickdillon can someone on the installer team take a look?

[taliandre49]

/test e2e-ibmcloud-ovn

[tthvo]

/test e2e-aws-ovn-public-ipv4-pool

I just wanted to see the result of this job :D This PR is the first 4.22 backport I can find :D

[taliandre49]

/test e2e-ibmcloud-ovn

[taliandre49]

CI jobe2e-ibmcloud-ovn failing due to identified bug https://redhat.atlassian.net/browse/OCPBUGS-84713

[openshift-ci]

@taliandre49: The following test 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-ibmcloud-ovn	4b94bd1	link	false	/test e2e-ibmcloud-ovn

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.

[taliandre49]

@patrickdillon Could you please point us to the correct individual on the installer team to assign approval for the PR and move it forward. Thank you!