NO-JIRA: Bump machine-api-operator to pull in authoritativeAPI fix

[damdo]

Ref: openshift/machine-api-operator#1386

[damdo]

@Karthik-K-N do we normally these PRs this manually before merging?

[Karthik-K-N]

@Karthik-K-N do we normally these PRs this manually before merging?

I hope you mean testing them before merging and yes we can do that.

@aman4433 would you be able to help us?

[damdo]

@Karthik-K-N yes that's what I meant :) thanks both!

[RadekManak]

/lgtm
/approve
/hold
@aman4433 unhold when you finish testing.

[aman4433]

Tested the controller locally by scaling the Machineset ipi420syd5-58wx9-worker from 3 to 4. Machine ipi420syd5-58wx9-worker-qptbm was created, and the corresponding node became Ready. All controllers in openshift-machine-api are running. Working as expected.

/lgtm
/unhold

amanshrivastava@Amans-MacBook-Pro machine-api-provider-powervs % oc get pods -n openshift-machine-api
NAME                                                  READY   STATUS    RESTARTS        AGE
cluster-autoscaler-operator-9fddc97db-k49n5           2/2     Running   1 (6h21m ago)   6h35m
cluster-baremetal-operator-6f5d7f6456-nn672           2/2     Running   1 (6h21m ago)   6h33m
control-plane-machine-set-operator-75759dc878-zd2br   1/1     Running   1 (6h21m ago)   6h35m
machine-api-controllers-b98b4cf9-rpxs7                7/7     Running   4 (6h21m ago)   6h25m

[openshift-ci]

@aman4433: changing LGTM is restricted to collaborators

Details

In response to this:

Tested the controller locally by scaling the Machineset ipi420syd5-58wx9-worker from 3 to 4. Machine ipi420syd5-58wx9-worker-qptbm was created, and the corresponding node became Ready. All controllers in openshift-machine-api are running. Working as expected.

/lgtm
/unhold

amanshrivastava@Amans-MacBook-Pro machine-api-provider-powervs % oc get pods -n openshift-machine-api
NAME                                                  READY   STATUS    RESTARTS        AGE
cluster-autoscaler-operator-9fddc97db-k49n5           2/2     Running   1 (6h21m ago)   6h35m
cluster-baremetal-operator-6f5d7f6456-nn672           2/2     Running   1 (6h21m ago)   6h33m
control-plane-machine-set-operator-75759dc878-zd2br   1/1     Running   1 (6h21m ago)   6h35m
machine-api-controllers-b98b4cf9-rpxs7                7/7     Running   4 (6h21m ago)   6h25m

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.

[Karthik-K-N]

Thanks @aman4433 for validating it.

/lgtm

/unhold

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aman4433, damdo, Karthik-K-N, RadekManak

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 [Karthik-K-N]

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

[Karthik-K-N]

/retest

[damdo]

/retitle NO-JIRA: Bump machine-api-operator to pull in authoritativeAPI fix

[damdo]

Thanks all! @Karthik-K-N @aman4433

[openshift-ci-robot]

@damdo: This pull request explicitly references no jira issue.

Details

In response to this:

Ref: openshift/machine-api-operator#1386

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-powervs-machine-controllers
This PR has been included in build ose-powervs-machine-controllers-container-v4.20.0-202507081544.p0.gf54657d.assembly.stream.el9.
All builds following this will include this PR.