-
Notifications
You must be signed in to change notification settings - Fork 93
Fixed bootVolume name bug #2297
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
Fixed bootVolume name bug #2297
Conversation
Hi @anshuman-agarwala. 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. |
✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
/ok-to-test |
2c49175
to
022ea96
Compare
} | ||
|
||
if volume.Name != "" { | ||
bootVolume.Volume.Name = core.StringPtr(volume.Name) |
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.
volume.Name
spec is intended to be assigned to bootVolume.Volume.Name
or bootVolume.Name
?
what would be the value of bootVolume.Volume.Name
post this change?
If unspecified, the name will
// be a hyphenated list of randomly-selected words.
is this the flow expectation?
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.
Yes, the boot volume name is expected to be random. This is required because when we add a volume name to the bootvolume the machine creation fails as each machine tries to create and mount a volume with the same name in their shared workspace which is not supported by IBMCloud.
/cc @Karthik-K-N |
@anshuman-agarwala Please update the release note in description. |
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.
/lgtm
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: anshuman-agarwala, mkumatag 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:
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 #2260
Special notes for your reviewer:
/area provider/ibmcloud
Release note: