-
Bug
-
Resolution: Done
-
Critical
-
None
-
Submariner 0.14.0, ACM 2.7.0
-
False
-
None
-
False
-
-
-
Important
-
No
Description of problem:
ACM 2.7 / Submariner 0.14.0
During execution of e2e tests using subctl, specific "dataplane" tests fails due to the container creation error.
The container is using nettest image.
The error of the pod boot up is:
state: terminated: containerID: cri-o://f651a0fd6525417a1122584feda9d024850cc6c3bf5441b94befb8fd0d022f20 exitCode: 2 finishedAt: "2022-11-29T12:37:10Z" message: | Ncat: Since April 2010, the default unit for -w timeout is seconds, so your time of "120" is 2.0 minutes. Use "120ms" for 120 milliseconds. QUITTING. reason: Error
The failure appears on the "Basic TCP connectivity" tests, like:
- [dataplane] Basic TCP connectivity tests across clusters without discovery when a pod connects via TCP to a remote pod when the pod is not on a gateway and the remote pod is on a gateway [It] should have sent the expected data from the pod to the other pod
- [dataplane] Basic TCP connectivity tests across clusters without discovery when a pod connects via TCP to a remote pod when the pod is on a gateway and the remote pod is on a gateway [It] should have sent the expected data from the pod to the other pod
- [dataplane] Basic TCP connectivity tests across clusters without discovery when a pod connects via TCP to a remote service when the pod is not on a gateway and the remote service is on a gateway [It] should have sent the expected data from the pod to the other pod
- links to