-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.13.z, 4.12.z, 4.14.z, 4.15
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
None
-
SDN Sprint 241
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Job Link- 1645698379981787136
Error Link- blob:https://prow.ci.openshift.org/9b34b56d-ebc6-44fd-8e54-42007e38d9fb
Observing testcase failure in latest 4.13 powerVS jobs. ERROR: link Events (openshiftapps.com)Apr 11 10:30:46.355: INFO: Couldn't detect KubeProxy mode - test failure may be expected: error running /usr/bin/kubectl --server=https://api.rdr-multiarch-XXX01.ocp-dev-ppc64le.com:6443 --kubeconfig=/tmp/kubeconfig-181626096 --namespace=e2e-services-523 exec kube-proxy-mode-detector – /bin/sh -x -c curl -q -s --connect-timeout 1 http://localhost:10249/proxyMode:stderr:+ curl -q -s --connect-timeout 1 http://localhost:10249/proxyMode command terminated with exit code 7 Apr 11 09:41:09.989: INFO: Service reachability failing with error: error running /usr/bin/kubectl --server=https://api.rdr-multiarch-XXX01.ocp-dev-ppc64le.com:6443 --kubeconfig=/tmp/kubeconfig-181626096 --namespace=e2e-services-1517 exec execpod-affinity8txkc -- /bin/sh -x -c nc -v -z -w 2 192.168.124.15 30994: Command stdout: stderr: + nc -v -z -w 2 192.168.124.15 30994 nc: connect to 192.168.124.15 port 30994 (tcp) timed out: Operation in progress command terminated with exit code 1 error: exit status 1
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: