Skip to content

Conversation

@damdo
Copy link
Member

@damdo damdo commented Jul 4, 2025

@openshift-ci openshift-ci bot requested review from RadekManak and nrb July 4, 2025 07:22
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 4, 2025

@damdo: 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/regression-clusterinfra-ibmcloud-ipi-mapi 7e124e2 link false /test regression-clusterinfra-ibmcloud-ipi-mapi

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.

@RadekManak
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 7, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 7, 2025
@damdo
Copy link
Member Author

damdo commented Jul 7, 2025

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 7, 2025
@damdo damdo changed the title Bump machine-api-operator to pull in authoritativeAPI fix OCPCLOUD-2986,OCPCLOUD-2985,OCPBUGS-56849: Bump machine-api-operator to pull in authoritativeAPI fix Jul 7, 2025
@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Jul 7, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 7, 2025

@damdo: This pull request references OCPCLOUD-2986 which is a valid jira issue.

This pull request references OCPCLOUD-2985 which is a valid jira issue.

This pull request references Jira Issue OCPBUGS-56849, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.20.0) matches configured target version for branch (4.20.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sunzhaohua2

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

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-ci openshift-ci bot requested a review from sunzhaohua2 July 7, 2025 10:31
@damdo
Copy link
Member Author

damdo commented Jul 7, 2025

/unhold

@damdo
Copy link
Member Author

damdo commented Jul 7, 2025

Regression passed but failed on the gathering phase.

@openshift-merge-bot openshift-merge-bot bot merged commit faf0276 into openshift:main Jul 7, 2025
11 of 12 checks passed
@openshift-ci-robot
Copy link

@damdo: Jira Issue OCPBUGS-56849: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-56849 has not been moved to the MODIFIED state.

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

[ART PR BUILD NOTIFIER]

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

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. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants