-
Notifications
You must be signed in to change notification settings - Fork 1.5k
OCPBUGS-65847: vsphere: add SkipIPAllocation to network devices #10125
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
base: main
Are you sure you want to change the base?
Conversation
Set SkipIPAllocation: true and disable DHCP4/DHCP6 on VSphereMachine network devices to prevent CAPV from waiting for VMware Tools to report IP addresses. This is appropriate when IP allocation is handled externally or when VMware Tools may not reliably report IPs to vCenter.
|
@rbbratta: This pull request references Jira Issue OCPBUGS-65847, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/hold dualstack-primaryv6 debug. |
|
[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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@rbbratta: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
Well at least it failed in a different place. |
Set SkipIPAllocation: true and disable DHCP4/DHCP6 on VSphereMachine network devices to prevent CAPV from waiting for VMware Tools to report IP addresses. This is appropriate when IP allocation is handled externally or when VMware Tools may not reliably report IPs to vCenter.