-
Bug
-
Resolution: Obsolete
-
Minor
-
None
-
4.13.z
Description of problem:
pip3 not avilable in ovnkube-node container and hence ovnkube-trace fails on detrace step
Version-Release number of selected component (if applicable):
4.13.3
How reproducible:
Always
Steps to Reproduce:
1. Create a OCP 4.13.3 cluster with OVN-k CNI 2. Run ovnkube-trace as follows: ./ovnkube-trace -src-namespace openshift-dns -src dns-default-xgcmt -dst-namespace openshift-dns -dst dns-default-6qjqc -udp -dst-port 53 I0707 00:44:27.469540 21772 ovs.go:90] Maximum command line arguments set to: 191102 ovn-trace source pod to destination pod indicates success from dns-default-xgcmt to dns-default-6qjqc ovn-trace destination pod to source pod indicates success from dns-default-6qjqc to dns-default-xgcmt ovs-appctl ofproto/trace source pod to destination pod indicates success from dns-default-xgcmt to dns-default-6qjqc ovs-appctl ofproto/trace destination pod to source pod indicates success from dns-default-6qjqc to dns-default-xgcmt I0707 00:44:29.523808 21772 ovnkube-trace.go:1182] Skipped ovn-detrace due to: "dependencies check failed: \"ovn-detrace error in pod ovnkube-node-d5t67, container ovnkube-node. Error 'command terminated with exit code 127', stdOut: ''\\n stdErr: bash: line 1: pip3: command not found\\n\""
Actual results:
ovnkube-trace fails with the pip3 library not avialable
Expected results:
ovnkube-trace should pass and necessary libraries should be avilable
Additional info:
- relates to
-
-
- Closed
-
