-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
openstack: Cloud config install config #611
Conversation
c8c561e
to
ade1e96
Compare
@flaper87 when I try this patch and log into the bootstrap node, I see that the MCO container keeps crashing with this error:
Looks like we'll need to do a corresponding change in there? Just flagging it here, because this prevents other containers and the master nodes from coming up and I didn't see you mention it in the message. |
@tomassedovic correct! There's no way to make this change without breaking MCO :( I have a WIP commit that fixes this in MCO already: https://github.com/openshift/machine-config-operator/compare/master...flaper87:cloud-provider-conf?expand=1#diff-36b9f3e22f35e4ae1cfd1ff70a12ca71R64 Thanks for flagging it, I should have mentioned it in the commit :) |
Right, and we can't fix it in MCO first, because it needs to vendor the changes in this commit, right? In that case, better do this sooner (as in now in this PR) rather than later, I'd say. |
ade1e96
to
3c603ac
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: flaper87 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 |
1ed7643
to
1c5d731
Compare
We need to pass the cloud's config data to the MCO in order to be able to configure the cloud provider openstack. This commit passes such data as part of the platform configuration since MCO consumes install-config to get the cluster conifguration. As part of this commit, we're now also validating the user's input to verify whether the cloud name passed is correct.
1c5d731
to
995d8ee
Compare
@abhinavdahiya @sallyom I've added the "ProviderConfig" data to the |
@flaper87: PR needs rebase. 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. |
@flaper87: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
we'll be addressing this differently. |
@flaper87: Closed this PR. In 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. |
We need to pass the cloud's config data to the MCO in order to be able
to configure the cloud provider openstack. This commit passes such data
as part of the platform configuration since MCO consumes install-config
to get the cluster conifguration.
As part of this commit, we're now also validating the user's input to
verify whether the cloud name passed is correct.
This PR depends on #588