-
Notifications
You must be signed in to change notification settings - Fork 72
[release-4.14] OCPBUGS-19849: Set dual-stack IPFamilyPriority for vSphere #283
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
[release-4.14] OCPBUGS-19849: Set dual-stack IPFamilyPriority for vSphere #283
Conversation
We have discovered that in dual-stack setups NodeAddresses field of the instance metadata contains only IPv4 addresses for VMs that do have both IPv4 and IPv6 addresses assigned (and detected by the VM agent). It has been traced back to the function responsible for populating this metadata field. We found out that for our configuration we always filter only IPv4 addresses even if running in dual-stack. Reason for that is that `IPFamilyPriority` has a value of `ipv4` even when running in a dual-stack setup. This causes an issue because this instance metadata is cross-checked with addresses provided by the kubelet as part of the `alpha.kubernetes.io/provided-node-ip` annotation. Without correct value of `IPFamilyPriority` we are thus removing all the IPv6 addresses. This PR takes advantage of the Service Networks configured by the user in install-config and the fact that we only allow 2 networks to be configured if the setup is dual-stack. Fixes: OCPBUGS-18641
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-18641 has been cloned as Jira Issue OCPBUGS-19849. Will retitle bug to link to clone. 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 kubernetes/test-infra repository. |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-19849, which is valid. The bug has been moved to the POST state. 6 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 kubernetes/test-infra repository. |
|
/lgtm Clean cherry-pick |
|
vsphere,dualstack clusterbot success https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-launch-vsphere-modern/1707054954306342912 |
|
|
|
/label qe-approved |
|
/approve |
|
/label backport-risk-assessed |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/label cherry-pick-approved |
|
@mkowalski: Can not set label cherry-pick-approved: Must be member in one of these teams: [] 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 kubernetes/test-infra repository. |
|
/label cherry-pick-approved |
|
@rbbratta: Can not set label cherry-pick-approved: Must be member in one of these teams: [] 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 kubernetes/test-infra repository. |
|
/label cherry-pick-approved |
|
@openshift-cherrypick-robot: 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/test-infra repository. I understand the commands that are listed here. |
|
vSphere test waiting for openshift/kubernetes#1730 to merge |
|
/hold |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-19849, which is valid. The bug has been moved to the POST state. 6 validation(s) were run on this bug
Requesting review from QA contact: 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 kubernetes/test-infra repository. |
|
/label cherry-pick-approved , based on test |
|
Still fighting with the vSphere storage issues via openshift/kubernetes#1730. They are hard-blocking the tests to pass even though the underlying issue (fixed upstream via kubernetes/kubernetes#120961) is not related to our change |
|
/unhold Based on Milind's successful test and the fact that periodics in o/release explicitly ignore in-tree storage tests I am okay with unholding in letting this merge. We will see very quickly (next nightly) if that broke anything, but I strongly believe that it will not happen |
|
@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-19849, which is valid. 6 validation(s) were run on this bug
Requesting review from QA contact: 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 kubernetes/test-infra repository. |
|
/test e2e-alibaba-ovn Blind retest, I don't need alibaba to pass in vsphere |
|
/override ci/prow/e2e-alibaba-ovn This was made to be required by accident, it shouldn't be needed |
|
@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/e2e-alibaba-ovn 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 kubernetes/test-infra repository. |
|
@openshift-cherrypick-robot: Jira Issue OCPBUGS-19849: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-19849 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
This is an automated cherry-pick of #279
/assign mkowalski