-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 1732858: unhardcode the cloud name for openstack #2122
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
Bug 1732858: unhardcode the cloud name for openstack #2122
Conversation
77fa8de to
3b3c07a
Compare
3b3c07a to
7db337b
Compare
|
/test e2e-openstack |
7db337b to
c042f68
Compare
|
/test e2e-openstack |
|
/assign |
|
/lgtm Looks good to me, thanks! I'm putting it on Feel free to remove the hold once |
|
/retest |
|
/test e2e-openstack |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
/test e2e-openstack |
1 similar comment
|
/test e2e-openstack |
c042f68 to
1e6c781
Compare
|
/hold cancel |
pkg/tfvars/openstack/openstack.go
Outdated
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.
why is the cloud name on master machine objects different from the the one that should actually be used??
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.
Yeah, it's not related here at all... I changed this.
Now, when the installer wants to read a local clouds.yaml file, it looks at "cloud" value from the install-config.yaml first, and, if there is nothing, it tries the default value "openstack".
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.
But when we create a system secret with a generated "clouds.yaml" item, it always sets the name as "openstack" there, which is good for consistency.
7962a4e to
065efa8
Compare
pkg/tfvars/openstack/openstack.go
Outdated
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.
this should part of the defaults.. not when passing those to terraform.
065efa8 to
ff6f1fa
Compare
ff6f1fa to
37f7816
Compare
37f7816 to
b4de924
Compare
To allow users to provide custom cloud names in the install config we need to remove the hardcoded 'openstack' name. To do so and to keep the compatibility with the current behavior, we read cloud name from the install config first, and if it's empty, set it to the value of OS_CLOUD env variable. If both values are not specified, then cloud name defaults to "openstack".
b4de924 to
b920e6c
Compare
|
@Fedosin: This pull request references a valid Bugzilla bug. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 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 kubernetes/test-infra repository. |
|
/approve |
|
/test e2e-openstack |
2 similar comments
|
/test e2e-openstack |
|
/test e2e-openstack |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, dprince, Fedosin, mandre, tomassedovic 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 |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@Fedosin: All pull requests linked via external trackers have merged. The Bugzilla bug has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
To allow users to provide custom cloud names in the install config we need to remove hardcoded 'openstack' name.
To do so and to keep the compatibility with the current behavior, we read cloud name from the install config first, and if it's empty, set it to the value of OS_CLOUD env variable. If both values are not specified, then cloud name defaults to "openstack".
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1732858