Details
-
Bug
-
Resolution: Done
-
Major
-
4.12.z, 4.11.z, 4.10.z
-
Low
-
No
-
0
-
WINC - Sprint 235
-
1
-
False
-
Description
This is a clone of issue OCPBUGS-11735. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-11306. The following is the description of the original issue:
—
Description
The node log collection test is failing in vSphere CI.
Example: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_windows-machine-config-operator/1534/pull-ci-openshift-windows-machine-config-operator-release-4.12-vsphere-e2e-operator/1641503527182274560
=== RUN TestWMCO/create/Node_Logs === RUN TestWMCO/create/Node_Logs/e2e-wm-5n5ng/kube-proxy/kube-proxy.exe.INFO 2023/03/30 20:02:05 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:02:24 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:02:39 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:02:54 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:03:09 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:03:24 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:03:39 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:03:54 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:04:09 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host 2023/03/30 20:04:12 unable to retrieve log kube-proxy/kube-proxy.exe.INFO from node e2e-wm-5n5ng: oc adm node-logs failed with exit code exit status 1 and output: : error: error trying to reach service: dial tcp [fd65:a1a8:60ad:271c::58]:10250: connect: no route to host
This seems to be occurring only on vsphere, in release-4.12 and below
It may or may not be related to an ipv6 address being used to talk to kubelet.
Acceptance Criteria
- node-logs test consistently passes
Attachments
Issue Links
- blocks
-
-
- Closed
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is cloned by
-
-
- Closed
-
- links to
- mentioned on
