Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

iPerf: client pod failure on ipv6 traffic required for dual-stack cluster #814

Closed
elenagerman opened this issue Jun 21, 2023 · 2 comments
Closed

Comments

@elenagerman
Copy link
Contributor

elenagerman commented Jun 21, 2023

Describe the bug
In the case of a dual-stack cluster, when ipv6 traffic is required, and even the '-6' option is provided, the 'iperf3 -c ' command will always use an ipv4 address.
The openshift preference in the case of dual-stack is always ipv4. And this is a reason the server pod will always have ipv4 as a main pod address (podIP value).

As a result, when '-6' option is used in this case and 'iperf3 -c ' will run to the ipv4 address, the pod execution fails.

To Reproduce
Steps to reproduce the behavior:

  1. Deploy dual-stack cluster
  2. apply this benchmark:
    `

apiVersion: ripsaw.cloudbulldozer.io/v1alpha1
kind: Benchmark
metadata:
name: iperf3-benchmark-iperf3
namespace: benchmark-operator
spec:
uuid: "3ac4f6c1-69f3-469d-aa9f-a81382a77007"
elasticsearch:
url: 'localhost'
clustername: kni-qe-3
metadata:
collection: true
privileged: true
serviceaccount: 'benchmark-operator'
targeted: false
workload:
name: iperf3
args:
image: "registry.kni-qe-3.lab.eng.rdu2.redhat.com:5000/cloud-bulldozer/iperf3:latest"
run_id: "100056"
pair: 1
port: 60001
transmit_type: time
transmit_value: 100
length_buffer: 500
streams: 1
extra_options_client: '-u -b 0 -6 -J -V'
pin: true
pin_server: "openshift-worker-3.kni-qe-3.lab.eng.rdu2.redhat.com"
pin_client: "openshift-worker-2.kni-qe-3.lab.eng.rdu2.redhat.com"

`
4. wait until client pod failure
5. oc describe client pod to see 'iperf3 -c addr' was used

Expected behavior
option to run iPerf ipv6 traffic on dual-stack cluster

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Browser [e.g. chrome, safari]
  • Version [e.g. 22]

Smartphone (please complete the following information):

  • Device: [e.g. iPhone6]
  • OS: [e.g. iOS8.1]
  • Browser [e.g. stock browser, safari]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

@elenagerman
Copy link
Contributor Author

maybe possible solution: #815

@elenagerman
Copy link
Contributor Author

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant