Skip to content

Conversation

@mdbooth
Copy link

@mdbooth mdbooth commented Feb 14, 2025

Failing to set this breaks from CAPI v1.9 onwards.

/hold

Failing to set this breaks from CAPI v1.9 onwards.
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 14, 2025
@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 Feb 14, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 14, 2025

@mdbooth: This pull request references OCPCLOUD-2857 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.19.0" version, but no target version was set.

Details

In response to this:

Failing to set this breaks from CAPI v1.9 onwards.

/hold

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.

@mdbooth
Copy link
Author

mdbooth commented Feb 14, 2025

The e2e tests will run this against CAPI 1.8. I have manually tested it against openshift/cluster-api#230 which updates to CAPI 1.9 and confirmed that it now works.

$ kc -n openshift-cluster-api get openstackclusters.infrastructure.cluster.x-k8s.io
NAME                     CLUSTER                  READY   NETWORK                                BASTION IP   AGE
mbooth-capi-test-9pmrl   mbooth-capi-test-9pmrl   true    12b9dc39-595f-4d89-b460-f4f813a23bdd                2m48s

@mdbooth
Copy link
Author

mdbooth commented Feb 14, 2025

/hold cancel

@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 Feb 14, 2025
@openshift-ci
Copy link

openshift-ci bot commented Feb 14, 2025

@mdbooth: 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/okd-scos-e2e-aws-ovn f67205c link false /test okd-scos-e2e-aws-ovn

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.

@EmilienM
Copy link
Member

how did we miss that!
/lgtm
/approve
/label acknowledge-critical-fixes-only

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

openshift-ci bot commented Feb 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: EmilienM

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 Feb 14, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit c4c0495 into openshift:main Feb 14, 2025
8 of 9 checks passed
@openshift-merge-bot openshift-merge-bot bot deleted the OCPCLOUD-2857 branch February 14, 2025 21:59
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: openstack-cluster-api-controllers
This PR has been included in build openstack-cluster-api-controllers-container-v4.19.0-202502150007.p0.gc4c0495.assembly.stream.el9.
All builds following this will include this PR.

@mdbooth
Copy link
Author

mdbooth commented Feb 15, 2025

how did we miss that!

It works on 1.8. It would be a regression in CAPI 1.9, but we're not running the defaulting webhook which would have prevented it.

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants