-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Bug 1895099: Create empty vSphere infra PlatformStatus in UPI #4352
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 1895099: Create empty vSphere infra PlatformStatus in UPI #4352
Conversation
This creates an empty infrastructure.Status.PlatformStatus.VSphere object during UPI installs. Prior to this change, the object has been nil during UPI installs. The object is optional, but a recent change to MCO templating[0] has a dependency on the object. [0]: openshift/machine-config-operator#2079
|
@patrickdillon: This pull request references Bugzilla bug 1895099, which is invalid:
Comment 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/test e2e-vsphere |
|
@patrickdillon: This pull request references Bugzilla bug 1895099, which is invalid:
Comment 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. |
|
Makes sense to me. I will let tests run and see if upi is green. |
|
@jcpowermac righly pointed out (on slack) this will not fix upgrades, not sure if this PR has merit on its own, i will look at an analogue mco fix |
|
/hold Hm it looks like these changes might just result in a mangled config file where the IP addresses are missing but the rest of the config file is present: https://github.com/openshift/machine-config-operator/blob/master/templates/common/on-prem/files/NetworkManager-resolv-prepender.yaml Before the mco changes, we wouldn't populate any of the config file: https://github.com/openshift/machine-config-operator/pull/2079/files#diff-88b9eeb5fb253707d42dfa34ac2143dda76d949209de64c032a8cd11a0d97c29 |
|
@patrickdillon: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/close |
|
@patrickdillon: Closed this PR. 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. |
This creates an empty infrastructure.Status.PlatformStatus.VSphere object during UPI installs. Prior to this change, the object has been nil during UPI installs. The object is optional, but a recent change to MCO templating0 has a dependency on the object.
cc @jcpowermac