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.10] OCPBUGS-11898: Disable IPv6 on Windows 2022 #1554
[release-4.10] OCPBUGS-11898: Disable IPv6 on Windows 2022 #1554
Conversation
aravindhp
commented
Apr 12, 2023
- [vpshere_ci] Disable IPv6 on Windows 2022
- [test] Use IPv6 disabled template for Windows 2022
To work around the issue with "oc adm node-logs" hitting an IPv6 address on IBM vCenter clusters, disable IPv6 on the Windows Server 2022 template. Update the README.md wrt disabling IPv6 along with other minor updates. (based on commit 7f27689)
Switch to using the IPv6 disabled template for Windows Server 2022 to mitigate issues seen in CI when the job lands in IBM vCenter where the DHCP server hands out IPv6 addresses causing `oc adm node-logs` test to fail. To be consistent update the machineset.sh script to also use the same template. (based on commit e419d3b)
@aravindhp: No Bugzilla bug is referenced in the title of this pull request. 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. |
Skipping CI for Draft Pull Request. |
/approve cancel |
/hold until release-4.11 backport for #1553 is opened and until the image is copied over to IBM vCenter |
/retitle [release-4.10] Disable IPv6 on Windows 2022 |
@aravindhp: No Bugzilla bug is referenced in the title of this pull request. 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 vsphere-e2e-operator |
/test platform-none-vsphere-e2e-operator Seeing a flake:
|
/test vsphere-e2e-operator |
/test platform-none-vsphere-e2e-operator Continuing to see:
|
One of the Windows Machines did not get assigned an IPv4 address but the other Machine did. /test vsphere-e2e-operator |
/test platform-none-vsphere-e2e-operator |
1 similar comment
/test platform-none-vsphere-e2e-operator |
/jira cherrypick OCPBUGS-11831 |
@aravindhp: Jira Issue OCPBUGS-11831 has been cloned as Jira Issue OCPBUGS-11898. 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. |
@aravindhp: No Bugzilla bug is referenced in the title of this pull request. 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. |
@aravindhp: This pull request references Jira Issue OCPBUGS-11898, 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. |
@aravindhp: No Bugzilla bug is referenced in the title of this pull request. Retaining the bugzilla/valid-bug label as it was manually added. 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. |
/jira refresh |
@aravindhp: This pull request references Jira Issue OCPBUGS-11898, which is valid. 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. |
/test platform-none-vsphere-e2e-operator Still seeing:
|
Thanks for working on this, |
/test platform-none-vsphere-e2e-operator |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sebsoto 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 |
/unhold |
/test vsphere-e2e-operator |
/hold Revision 8935ede was retested 3 times: holding |
IBM vCenter connections are flaky /retest-required |
/hold cancel |
@aravindhp: all tests passed! 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. |
1d41080
into
openshift:release-4.10
@aravindhp: Jira Issue OCPBUGS-11898: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-11898 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. |