-
Notifications
You must be signed in to change notification settings - Fork 280
🐛 Fix panic when OpenStackCluster.Status.Network is nil in HCP scenarios #2635
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
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for kubernetes-sigs-cluster-api-openstack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Hi @bnallapeta. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
Marking it as Draft as we are working on the e2e tests. This is the approach being taken for e2e. Let me know your thoughts.
Right now, we are somewhere in the 3rd/4th step and are facing the below challenges: First, when we specify our Kamaji as a control plane provider in e2e_conf.yaml and name it as kamaji this error pops up:
Second, if we try to bypass and name this kamaji as kubeadm, kamaji doesn't get installed as such and later on, we face issues with finding Kamaji CRDs
Would really appreciate your help on this to move forward. cc @orkhan-os |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Appreciate this is just a draft, but I had a quick look over it anyway.
3321655
to
0ab4e3c
Compare
/ok-to-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code change lgtm. Just some weirdness in the tests which needs clearing up.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Am I understanding correctly that this changes the behavior for security groups on OpenStackMachines? We cannot sneak in that change as a bug fix (🐛 ). If we want to change it (and I am not sure we do), the PR has to be marked as a breaking change (
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code looks good to me know. Added some comments for the documentation
@lentzi90 addressed all the comments on docs. Just one conversation yet to be resolved. Also, with this commit, I updated all references of tenant cluster to workload cluster to stay in touch with CAPI/CAPO nomenclature. |
Signed-off-by: Bharath Nallapeta <[email protected]> addressed PR comments on secGroups Signed-off-by: Bharath Nallapeta <[email protected]>
Signed-off-by: Bharath Nallapeta <[email protected]>
bd01438
to
cefcbae
Compare
Signed-off-by: Bharath Nallapeta <[email protected]> Signed-off-by: Bharath Nallapeta <[email protected]> Signed-off-by: Bharath Nallapeta <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm ok with this now. @mdbooth do you have time to take another look also?
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lentzi90 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 |
What this PR does / why we need it:
Fixes a nil pointer panic in OpenStackMachineReconciler when OpenStackCluster.Status.Network is nil, which occurs in Hosted Control Plane scenarios. The controller now gracefully handles missing cluster network by checking for nil before access and returning a terminal error instead of panicking. Also adds comprehensive HCP E2E test suite.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #2380
TODOs:
/hold