-
Notifications
You must be signed in to change notification settings - Fork 33
OCPCLOUD-2857: Set infrastructureRef.Namespace in Cluster object #357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Failing to set this breaks from CAPI v1.9 onwards.
|
@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. DetailsIn response to this:
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. |
|
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. |
|
/hold cancel |
|
@mdbooth: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
how did we miss that! |
|
[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 DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
[ART PR BUILD NOTIFIER] Distgit: openstack-cluster-api-controllers |
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. |
Failing to set this breaks from CAPI v1.9 onwards.
/hold