Skip to content

Conversation

@damdo
Copy link
Member

@damdo damdo commented Jun 19, 2025

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 19, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 19, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@damdo damdo force-pushed the bump-mao-authoritativeAPI-fix branch from b3c81e3 to b387a5b Compare June 27, 2025 06:54
@damdo damdo changed the title Bump machine-api-operator to pull in authoritativeAPI fix OCPCLOUD-2986,OCPBUGS-56849: Bump machine-api-operator to pull in authoritativeAPI fix Jun 27, 2025
@damdo damdo marked this pull request as ready for review June 27, 2025 06:54
@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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jun 27, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jun 27, 2025

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

This pull request references Jira Issue OCPBUGS-56849, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED 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.

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#1380

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 removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 27, 2025
@openshift-ci openshift-ci bot requested review from elmiko and racheljpg June 27, 2025 06:56
@RadekManak
Copy link
Contributor

/lgtm
/approve

@damdo
Copy link
Member Author

damdo commented Jun 27, 2025

/assign @RadekManak @racheljpg @mdbooth

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

openshift-ci bot commented Jun 27, 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 Jun 27, 2025
@damdo
Copy link
Member Author

damdo commented Jun 27, 2025

/test unit

@damdo
Copy link
Member Author

damdo commented Jun 28, 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 Jun 28, 2025
@damdo damdo force-pushed the bump-mao-authoritativeAPI-fix branch from b387a5b to e9dce35 Compare July 3, 2025 14:45
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 3, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jul 3, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 3, 2025

@damdo: This pull request references OCPCLOUD-2986 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

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-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Jul 3, 2025
@openshift-ci openshift-ci bot requested a review from sunzhaohua2 July 3, 2025 14:48
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 3, 2025

@damdo: This pull request references OCPCLOUD-2986 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

Details

In response to this:

Ref: openshift/machine-api-operator#1386

TODO:

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.

@damdo damdo changed the title OCPCLOUD-2986,OCPBUGS-56849: 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 3, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 3, 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

TODO:

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.

@RadekManak
Copy link
Contributor

/lgtm

@damdo damdo force-pushed the bump-mao-authoritativeAPI-fix branch from e9dce35 to 9edd48c Compare July 4, 2025 07:07
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Jul 4, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 4, 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

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.

@damdo
Copy link
Member Author

damdo commented Jul 4, 2025

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 4, 2025
@damdo
Copy link
Member Author

damdo commented Jul 4, 2025

/retest

@damdo
Copy link
Member Author

damdo commented Jul 4, 2025

/test e2e-aws-serial

1 similar comment
@damdo
Copy link
Member Author

damdo commented Jul 4, 2025

/test e2e-aws-serial

@damdo
Copy link
Member Author

damdo commented Jul 5, 2025

/test regression-clusterinfra-aws-ipi-mapi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 5, 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-aws-ipi-mapi 9edd48c link false /test regression-clusterinfra-aws-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.

@damdo
Copy link
Member Author

damdo commented Jul 7, 2025

Regression only failed collecting the must-gather. Happy with the testing.

/unhold

@RadekManak
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 7, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 65dc832 into openshift:main Jul 7, 2025
13 of 14 checks passed
@openshift-ci-robot
Copy link
Contributor

@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
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-api-provider-aws
This PR has been included in build ose-machine-api-provider-aws-container-v4.20.0-202507071042.p0.g65dc832.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.

6 participants