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 creation failed for ipv6 traffic #813

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

iPerf client pod creation failed for ipv6 traffic #813

elenagerman opened this issue Jun 21, 2023 · 2 comments

Comments

@elenagerman
Copy link
Contributor

Describe the bug
When the ipv6 address is used for traffic generation, and this is the only ip version defined for the server ->
item.status.podIP getting ipv6 ip format value, "podIP": "fd01:0:0:6::bd" as an example

As a result, the client pod failed to create because of the name format failure; only '.' and '_' are acceptable in a name string (not ':').

To Reproduce
Steps to reproduce the behavior:

  1. Deploy ipv6 (only) cluster

  2. try to apply:
    `
    kind: Job
    apiVersion: batch/v1
    metadata:
    name: 'iperf3-client-fd01:0:0:6::85-2f8af690'
    namespace: 'benchmark-operator'
    spec:
    backoffLimit: 0
    activeDeadlineSeconds: 3600
    template:
    metadata:
    labels:
    app: iperf3-bench-client-2-2f8af690
    benchmark-uuid: "74a7cc28-c5ea-4571-82c7-632ecba88eb2"
    spec:
    affinity:
    podAntiAffinity:
    preferredDuringSchedulingIgnoredDuringExecution:
    - weight: 100
    podAffinityTerm:
    labelSelector:
    matchExpressions:
    - key: app
    operator: In
    values:
    - iperf3-bench-server-1-2f8af690
    topologyKey: kubernetes.io/hostname
    containers:

    • name: benchmark
      image: "registry.kni-qe-3.lab.eng.rdu2.redhat.com:5000/cloud-bulldozer/iperf3:latest"
      imagePullPolicy: Always
      command: ["/bin/sh", "-c"]
      args:
      • "iperf3 -c fd01:0:0:6::85
        -p 60001
        --time 100
        -l 500
        -P 1
        -u -b 0 -J -V"
        restartPolicy: Never
        nodeSelector:
        kubernetes.io/hostname: 'openshift-worker-2.kni-qe-3.lab.eng.rdu2.redhat.com'
        serviceAccountName: benchmark-operator
  3. [[email protected] ~]$ oc apply -f test2.yaml
    The Job "iperf3-client-2fd01:0:0:6::85-2f8af690" is invalid:

  • metadata.name: Invalid value: "iperf3-client-2fd01:0:0:6::85-2f8af690": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is 'a-z0-9?(.a-z0-9?)*')
  • metadata.labels: Invalid value: "iperf3-client-2fd01:0:0:6::85-2f8af690": a valid label must be an empty string or consist of alphanumeric characters, '-', '' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9.]*)?[A-Za-z0-9])?')
  • spec.template.labels: Invalid value: "iperf3-client-2fd01:0:0:6::85-2f8af690": a valid label must be an empty string or consist of alphanumeric characters, '-', '' or '.', and must start and end with an alphanumeric character (e.g. 'MyValue', or 'my_value', or '12345', regex used for validation is '(([A-Za-z0-9][-A-Za-z0-9.]*)?[A-Za-z0-9])?')

Expected behavior
client pod should be created

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

I'm not so sure about solution, but it could be something like this: #812

@stale
Copy link

stale bot commented Sep 17, 2023

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the not_ready label Sep 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant