Open elenagerman opened 1 year ago
I'm not so sure about solution, but it could be something like this: https://github.com/cloud-bulldozer/benchmark-operator/pull/812
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.
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:
Deploy ipv6 (only) cluster
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:
[kni@registry.kni-qe-3 ~]$ oc apply -f test2.yaml The Job "iperf3-client-2fd01:0:0:6::85-2f8af690" is invalid:
Expected behavior client pod should be created
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.