Skip to content

Conversation

@tthvo
Copy link
Member

@tthvo tthvo commented Nov 22, 2025

Since kubernetes-sigs/cluster-api-provider-aws#5720 is merged, upstream CAPA is now compatible with CAPI v1.11. Thus, we can vendor the latest commit on upstream main and remove the hack in #10060

This PR bumps CAPA to latest version on upstream main and syncs top-level go.mod and controller's go.mod.

/label platform/aws

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 22, 2025
@openshift-ci-robot
Copy link
Contributor

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

In response to this:

Since kubernetes-sigs/cluster-api-provider-aws#5720 is merged, upstream CAPA is now compatible with CAPI v1.11. Thus, we can vendor the latest commit on upstream main and remove the hack in #10060

This PR bumps CAPA to latest version on upstream main and syncs top-level go.mod and controller's go.mod.

/label platform/aws

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.

@tthvo
Copy link
Member Author

tthvo commented Nov 22, 2025

/retest

@tthvo
Copy link
Member Author

tthvo commented Nov 25, 2025

/retest
/test e2e-aws-ovn-public-subnets e2e-aws-ovn-public-ipv4-pool e2e-aws-ovn-custom-iam-profile e2e-aws-overlay-mtu-ovn-1200

@tthvo
Copy link
Member Author

tthvo commented Nov 25, 2025

/retest

Side note: The 2 runs ci/prow/e2e-aws-overlay-mtu-ovn-1200 and ci/prow/e2e-aws-ovn-custom-iam-profile appeared to time out at deprovision step because they took more than 1hr (lots of jobs are running).

However, they both completed successfully. So, there is nothing concerning here or even related to this change.

level=info msg=Time elapsed: 1h7m21s
level=info msg=Uninstallation complete! 

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 26, 2025

@tthvo: 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-aws-ovn-heterogeneous 64cdab8 link false /test e2e-aws-ovn-heterogeneous

Full PR test history. Your PR dashboard.

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.

@tthvo
Copy link
Member Author

tthvo commented Nov 26, 2025

Okayy, it looks like nothing is broken 😁

@tthvo
Copy link
Member Author

tthvo commented Dec 3, 2025

/verified by ci/prow/e2e-aws-ovn

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Dec 3, 2025
@openshift-ci-robot
Copy link
Contributor

@tthvo: This PR has been marked as verified by ci/prow/e2e-aws-ovn.

In response to this:

/verified by ci/prow/e2e-aws-ovn

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.

@sadasu
Copy link
Contributor

sadasu commented Dec 3, 2025

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Dec 3, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sadasu

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

The pull request process is described here

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 Dec 3, 2025
@patrickdillon
Copy link
Contributor

/lgtm
/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Dec 3, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 3, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 74b692f and 2 for PR HEAD 64cdab8 in total

@openshift-merge-bot openshift-merge-bot bot merged commit f436744 into openshift:main Dec 3, 2025
39 of 40 checks passed
@tthvo tthvo deleted the bump-capa branch December 3, 2025 22:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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. platform/aws verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants