Skip to content

Conversation

@rbbratta
Copy link
Contributor

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.

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.
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Nov 24, 2025
@openshift-ci-robot
Copy link
Contributor

@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
  • bug is open, matching expected state (open)
  • bug target version (4.21.0) matches configured target version for branch (4.21.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sgaoshang

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

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.

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.

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Nov 24, 2025
@openshift-ci openshift-ci bot requested a review from sgaoshang November 24, 2025 22:25
@rbbratta
Copy link
Contributor Author

/hold

dualstack-primaryv6 debug.

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 24, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 24, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jcpowermac for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 25, 2025

@rbbratta: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn 9ab62c0 link true /test e2e-aws-ovn
ci/prow/e2e-vsphere-ovn-disk-setup-techpreview 9ab62c0 link false /test e2e-vsphere-ovn-disk-setup-techpreview

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.

@rbbratta
Copy link
Contributor Author

Well at least it failed in a different place.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants