-
Bug
-
Resolution: Done
-
Major
-
None
-
ACM 2.6.Z
-
False
-
None
-
False
-
-
-
No
This is a followup bug reported and fixed in 0.14.1
https://issues.redhat.com/browse/ACM-2211
And backported into 0.13.3
https://github.com/submariner-io/subctl/pull/460
The following error seen in the pod that spawn up to check the kube proxy mode:
query-iface-list:
Container ID: cri-o://3d0e9f4536fa05dac77665f1e844f4b93f586ca6c67f765d4f23e20f603820ff
Image: registry.redhat.io/rhacm2/nettest-rhel8:v0.13.3
Image ID: registry.redhat.io/rhacm2/nettest-rhel8@sha256:6cfc0443e71b5a51623a9e2d527aa241f7ec3b2624136dc5fafe9194ccd5b3d3
Port: <none>
Host Port: <none>
Command:
sh
-c
$(COMMAND) >/dev/termination-log 2>&1 || exit 0
State: Terminated
Reason: Completed
Message: sh: ip: command not found Exit Code: 0
As seen from the output, the "ip" command within the pod is not found.
Looks like we forgot to backport this midstream patch to 0.13.
https://gitlab.cee.redhat.com/acm-cpaas-midstream/submariner-operator-midstream/-/merge_requests/102
