Support "none" cloudprovider#119
Conversation
|
/retest |
1 similar comment
|
/retest |
frobware
left a comment
There was a problem hiding this comment.
LGTM, but wondering why the "libvirt" and "none" testcases are different than aws for the expected cloudprovider field.
| hasExtendedArguments: true, | ||
| }, { | ||
| installConfig: "platform:\n libvirt: {}\n", | ||
| cloudProvider: "", |
There was a problem hiding this comment.
Given the "aws" test case, how come this is not "libvirt"? Perhaps I didn't look closely enough but I see for libvirt we return return observerConfig, errs - curious as to why "aws" is more explicit.
There was a problem hiding this comment.
This var is not being checked, as the func would immediately return observedConfig so in test ObserveCloudProviderNames would return immediately.
Reworked the test:
cloudProvideris not initialized for none and libvirt- test struct has
cloudProviderNum- expected number of cloudproviders - test now ensures expected and actual number of cloudproviders are equals
There was a problem hiding this comment.
I think cloudProviderNum is better expressed as cloudProviderCount. For me (at least) Num looks like an index.
There was a problem hiding this comment.
Right, I was choosing between these two, renamed to Count
afbad6d to
ad6a8ef
Compare
ad6a8ef to
95ab7b5
Compare
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: frobware, vrutkovs 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 |
|
/test e2e-aws |
| case platform["libvirt"] != nil: | ||
| // this means we are using libvirt | ||
| return observedConfig, errs | ||
| case platform["none"] != nil: |
There was a problem hiding this comment.
Does the none need to be specifies explicitly? Just asking what is the difference when the cloud provider is not specified and when it is set to none.
There was a problem hiding this comment.
none is the platform name in the installer, not cloudprovider name
After openshift/installer#982 was merged BYOR installs use
platform: none. Our install waits for all CVO operators to complete successfully, but kube-controller-manager-operator fails with this setup:This PR adds a support for this platform (as libvirt it doesn't modify
extendedArguments) and updates tests to verify these three cases.Don't know how to test that config was not modified, but I could extend the tests later on.ImplementedVerified that it unblocks
platform: noneinstallsFixes #100