OCPBUGS-83611: PowerVS: update release 4.22 CAPI to v0.12.2 by hamzy · Pull Request #10509 · openshift/installer

hamzy · 2026-04-16T16:10:36Z

Unfortunately, we could not backport PR10488 due to the size.

We are updating the PowerVS CAPI to v0.12.2

$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./cluster-api/providers/ibmcloud/go.mod
require sigs.k8s.io/cluster-api-provider-ibmcloud v0.12.2
        sigs.k8s.io/cluster-api v1.11.8 // indirect
$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./cluster-api/cluster-api/go.mod
require sigs.k8s.io/cluster-api v1.11.3
$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./go.mod
        sigs.k8s.io/cluster-api v1.11.8
        sigs.k8s.io/cluster-api-provider-aws/v2 v2.10.1-0.20260226000023-67627b2da0df
        sigs.k8s.io/cluster-api-provider-azure v1.21.1-0.20250929163617-2c4eaa611a39
        sigs.k8s.io/cluster-api-provider-gcp v1.10.1-0.20251030112604-5c2bfd5aadb3
        sigs.k8s.io/cluster-api-provider-ibmcloud v0.12.2
        sigs.k8s.io/cluster-api-provider-openstack v0.13.0
        sigs.k8s.io/cluster-api-provider-vsphere v1.14.0
        sigs.k8s.io/cluster-api-provider-azure => github.com/mboersma/cluster-api-provider-azure v0.3.1-0.20251030205607-3161b9cc8d3e

In the LoadBalancers struct, there is an AdditionalListeners field. That struct has an optional Protocol field. The PowerVS CAPI provider assumes incorrectly that this field always has a string pointer.

coderabbitai · 2026-04-16T16:10:47Z

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: Pro Plus

Run ID: 71d5267b-55ee-4344-a992-a5cbd0a950e5

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

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

openshift-ci-robot · 2026-04-16T16:11:22Z

@hamzy: This pull request references Jira Issue OCPBUGS-83611, which is invalid:

expected Jira Issue OCPBUGS-83611 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

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:

Unfortunately, we could not backport PR10488 due to the size.

We are updating the PowerVS CAPI to v0.12.2

$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./cluster-api/providers/ibmcloud/go.mod
require sigs.k8s.io/cluster-api-provider-ibmcloud v0.12.2
       sigs.k8s.io/cluster-api v1.11.8 // indirect
$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./cluster-api/cluster-api/go.mod
require sigs.k8s.io/cluster-api v1.11.3
$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./go.mod
       sigs.k8s.io/cluster-api v1.11.8
       sigs.k8s.io/cluster-api-provider-aws/v2 v2.10.1-0.20260226000023-67627b2da0df
       sigs.k8s.io/cluster-api-provider-azure v1.21.1-0.20250929163617-2c4eaa611a39
       sigs.k8s.io/cluster-api-provider-gcp v1.10.1-0.20251030112604-5c2bfd5aadb3
       sigs.k8s.io/cluster-api-provider-ibmcloud v0.12.2
       sigs.k8s.io/cluster-api-provider-openstack v0.13.0
       sigs.k8s.io/cluster-api-provider-vsphere v1.14.0
       sigs.k8s.io/cluster-api-provider-azure => github.com/mboersma/cluster-api-provider-azure v0.3.1-0.20251030205607-3161b9cc8d3e

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.

hamzy · 2026-04-16T16:20:39Z

/jira refresh

openshift-ci-robot · 2026-04-16T16:20:45Z

@hamzy: This pull request references Jira Issue OCPBUGS-83611, which is invalid:

expected dependent Jira Issue OCPBUGS-83327 to target a version in 5.0.0, but it targets "5.0" instead

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.

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.

hamzy · 2026-04-16T16:22:25Z

/jira refresh

openshift-ci-robot · 2026-04-16T16:22:33Z

@hamzy: This pull request references Jira Issue OCPBUGS-83611, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.22.0) matches configured target version for branch (4.22.0)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note text is set and does not match the template
dependent bug Jira Issue OCPBUGS-83327 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
dependent Jira Issue OCPBUGS-83327 targets the "5.0.0" version, which is one of the valid target versions: 5.0.0
bug has dependents

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.

hamzy · 2026-04-16T16:27:53Z

/test e2e-powervs-capi-ovn

hamzy · 2026-04-16T16:35:43Z

/assign tthvo

tthvo

/lgtm
/approve

tthvo · 2026-04-16T16:42:20Z

/cc @patrickdillon

for backport-risk-accessed :D

openshift-ci · 2026-04-16T16:42:45Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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:

~~OWNERS~~ [tthvo]

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

mjturek · 2026-04-16T17:47:50Z

/verified by mjturek

openshift-ci-robot · 2026-04-16T17:48:03Z

@mjturek: This PR has been marked as verified by mjturek.

Details

In response to this:

/verified by mjturek

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.

hamzy · 2026-04-16T17:52:19Z

/test e2e-ibmcloud-ovn

hamzy · 2026-04-16T18:27:30Z

/test e2e-powervs-capi-ovn

hamzy · 2026-04-16T20:01:39Z

ibmcloud succeeded
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_installer/10509/pull-ci-openshift-installer-release-4.22-e2e-ibmcloud-ovn/2044836337571336192/artifacts/e2e-ibmcloud-ovn/ipi-install-install/build-log.txt

hamzy · 2026-04-16T20:43:34Z

PowerVS did eventually succeed
https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/pr-logs/pull/openshift_installer/10509/pull-ci-openshift-installer-release-4.22-e2e-powervs-capi-ovn/2044845169655681024/artifacts/e2e-powervs-capi-ovn/ipi-install-powervs-install/build-log.txt

hamzy · 2026-04-17T00:42:52Z

/retest-required

openshift-ci · 2026-04-17T04:41:29Z

@hamzy: 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/gcp-private	`c78d867`	link	false	`/test gcp-private`
ci/prow/e2e-gcp-xpn-custom-dns	`c78d867`	link	false	`/test e2e-gcp-xpn-custom-dns`
ci/prow/e2e-gcp-xpn-dedicated-dns-project	`c78d867`	link	false	`/test e2e-gcp-xpn-dedicated-dns-project`
ci/prow/e2e-aws-ovn-single-node	`c78d867`	link	false	`/test e2e-aws-ovn-single-node`
ci/prow/gcp-custom-endpoints-proxy-wif	`c78d867`	link	false	`/test gcp-custom-endpoints-proxy-wif`
ci/prow/e2e-aws-ovn-heterogeneous	`c78d867`	link	false	`/test e2e-aws-ovn-heterogeneous`
ci/prow/e2e-azure-ovn-shared-vpc	`c78d867`	link	false	`/test e2e-azure-ovn-shared-vpc`
ci/prow/e2e-powervs-capi-ovn	`c78d867`	link	false	`/test e2e-powervs-capi-ovn`
ci/prow/e2e-gcp-ovn-xpn	`c78d867`	link	false	`/test e2e-gcp-ovn-xpn`
ci/prow/e2e-gcp-secureboot	`c78d867`	link	false	`/test e2e-gcp-secureboot`
ci/prow/e2e-gcp-custom-endpoints	`c78d867`	link	false	`/test e2e-gcp-custom-endpoints`
ci/prow/e2e-gcp-ovn-byo-vpc	`c78d867`	link	false	`/test e2e-gcp-ovn-byo-vpc`
ci/prow/e2e-azurestack	`c78d867`	link	false	`/test e2e-azurestack`

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.

patrickdillon · 2026-04-17T15:24:13Z

/label backport-risk-assessed

openshift-ci-robot · 2026-04-17T15:29:24Z

@hamzy: Jira Issue Verification Checks: Jira Issue OCPBUGS-83611
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-83611 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Unfortunately, we could not backport PR10488 due to the size.

We are updating the PowerVS CAPI to v0.12.2

$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./cluster-api/providers/ibmcloud/go.mod
require sigs.k8s.io/cluster-api-provider-ibmcloud v0.12.2
       sigs.k8s.io/cluster-api v1.11.8 // indirect
$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./cluster-api/cluster-api/go.mod
require sigs.k8s.io/cluster-api v1.11.3
$ egrep '(cluster-api-provider-ibmcloud|sigs.k8s.io/cluster-api)' ./go.mod
       sigs.k8s.io/cluster-api v1.11.8
       sigs.k8s.io/cluster-api-provider-aws/v2 v2.10.1-0.20260226000023-67627b2da0df
       sigs.k8s.io/cluster-api-provider-azure v1.21.1-0.20250929163617-2c4eaa611a39
       sigs.k8s.io/cluster-api-provider-gcp v1.10.1-0.20251030112604-5c2bfd5aadb3
       sigs.k8s.io/cluster-api-provider-ibmcloud v0.12.2
       sigs.k8s.io/cluster-api-provider-openstack v0.13.0
       sigs.k8s.io/cluster-api-provider-vsphere v1.14.0
       sigs.k8s.io/cluster-api-provider-azure => github.com/mboersma/cluster-api-provider-azure v0.3.1-0.20251030205607-3161b9cc8d3e

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-robot · 2026-04-18T03:25:49Z

Fix included in release 4.22.0-0.nightly-2026-04-17-213419

hamzy added 4 commits April 16, 2026 11:02

PowerVS: Fix optional Protocol field in AdditionalListeners

4055aae

In the LoadBalancers struct, there is an AdditionalListeners field. That struct has an optional Protocol field. The PowerVS CAPI provider assumes incorrectly that this field always has a string pointer.

Update ibmcloud-infrastructure-components.yaml

0255a90

Vendoring go.* changes

aaec5fb

Vendoring the rest changes

c78d867

hamzy changed the title ~~Power vs2 update capi v0.12.2~~ OCPBUGS-83611: PowerVS: update release 4.22 CAPI to v0.12.2 Apr 16, 2026

openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Apr 16, 2026

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 16, 2026

openshift-ci bot requested review from mjturek and pawanpinjarkar April 16, 2026 16:12

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 16, 2026

openshift-ci bot assigned tthvo Apr 16, 2026

tthvo reviewed Apr 16, 2026

View reviewed changes

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 16, 2026

openshift-ci bot requested a review from patrickdillon April 16, 2026 16:42

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 16, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 16, 2026

openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 17, 2026

openshift-merge-bot bot merged commit dfb58c0 into openshift:release-4.22 Apr 17, 2026
33 of 46 checks passed

Conversation

hamzy commented Apr 16, 2026

Uh oh!

coderabbitai bot commented Apr 16, 2026

Review skipped

Uh oh!

openshift-ci-robot commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

openshift-ci-robot commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

openshift-ci-robot commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

tthvo left a comment

Choose a reason for hiding this comment

Uh oh!

tthvo commented Apr 16, 2026

Uh oh!

openshift-ci bot commented Apr 16, 2026

Uh oh!

mjturek commented Apr 16, 2026

Uh oh!

openshift-ci-robot commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

hamzy commented Apr 16, 2026

Uh oh!

hamzy commented Apr 17, 2026

Uh oh!

openshift-ci bot commented Apr 17, 2026

Uh oh!

patrickdillon commented Apr 17, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 17, 2026

Uh oh!

openshift-merge-robot commented Apr 18, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants