-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Revert "Check if VIP IPs overlap with machine CIDR provided during vsphere installation" #4779
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
Revert "Check if VIP IPs overlap with machine CIDR provided during vsphere installation" #4779
Conversation
…ded during vsphere installation"
|
@staebler: This pull request references Bugzilla bug 1918469, which is valid. 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. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
#4754 was also causing issues for https://github.com/openshift/release/blob/2b486afdfb79bb8361e93058d37acdd234501baf/ci-operator/config/openshift/windows-machine-config-operator/openshift-windows-machine-config-operator-master.yaml#L66-L71, where the workflow used does not set the machine CIDR. |
|
/bugzilla ? |
|
@staebler: No Bugzilla bug is referenced in the title of this pull request. 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. |
|
/test e2e-vsphere |
|
/override ci/prow/e2e-aws-upgrade |
|
@staebler: Overrode contexts on behalf of staebler: ci/prow/e2e-aws-upgrade 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 |
|
/hold for vsphere tests |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: staebler 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 |
|
/lgtm |
|
/retest |
|
@staebler I am seeing in some of the tests (e2e-vsphere): Will the tests pass without fixing this? |
So far, I do not have any reason to believe that the error is not transient. Some of the jobs were able to build the upi-installer image (eg, images, e2e-metal-single-node-live-iso). /retest |
|
Any reason to just not allow the survey to ask for machine network? I realize the survey should be minimal, but this one additional question would be useful. We run into this problem on the baremetal validations (cc: @kirankt) |
@stbenjam We may fall back to that. In the case of vSphere, however, the user has been able to create and use clusters without issue for a long time now without having the machine CIDR match up with the actual machine network. There does not appear to be anything in the cluster that cares. And the installer does not care, since the installer is not directing instances into particular networks like it does for say AWS. We are looking into whether we can get the machine CIDR from the vSphere network at install time to fill out the machine CIDR in the install config on behalf of the user. |
|
/retest |
1 similar comment
|
/retest |
|
@staebler: 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. |
|
Both vsphere jobs passed. |
|
/override ci/prow/e2e-aws-upgrade |
|
@staebler: Overrode contexts on behalf of staebler: ci/prow/e2e-aws-upgrade 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. |
Reverts #4754
When using the survey flow, the machine CIDR is not populated. This causes the installation to fail, unless the VIPs happen to be within the default machine CIDR.