Ports getting assigned incorrectly for client-server pairs in uperf workload (Multiple pairs use case) about benchmark-operator

[mukrishn]

Good find, recent CI executions are failing on running more than 1 pair. Airflow logs have executions of 1, 2 & 4 pairs but results are available only for single pair.

[mukrishn]

Airflow task marked that test as completed because of false positive status of the benchmark resource. Client pods gets completed even on 100% packet loss and hence benchmark gets completed successfully as well. Need to fix that in the uperf wrapper script.

[jtaleric]

Airflow task marked that test as completed because of false positive status

Can you elaborate here? In Airflow, is it just ignoring the status code?

Client pods gets completed even on 100% packet loss and hence benchmark gets completed successfully as well.

😨

[mukrishn]

Can you elaborate here? In Airflow, is it just ignoring the status code?

It is not an Airflow problem, we observed the same behavior even without it.
It's because the benchmark wrapper not failing it in this case(screenshot), instead client pod goes to completed state and benchmark resource as well.

[vishnuchalla]

Yes. Even though the client pod has a failure. The benchmark status is marked as complete.