-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.19
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When converting an existing IPv6 single-stack cluster to dual-stack, the pods that were already running are not getting IPv4 addresses after the cluster becomes dual-stack.
Version-Release number of selected component (if applicable): 4.19
How reproducible: Always
Steps to Reproduce:
1. Deploy IPv6 cluster and a test workload
2. Follow this doc for moving to dual-stack
3. Once the process completes, check pod IPs. It will have only IPv6 addresses.
Actual results:
Pod only has IPv6 addresses:
hostIP: 2620:52:0:1308::5 hostIPs: - ip: 2620:52:0:1308::5 - ip: 192.168.111.5 phase: Running podIP: fd01:0:0:1::1fe podIPs: - ip: fd01:0:0:1::1fe
If I restart the pod (this shouldn't be required):
hostIP: 2620:52:0:1308::5 hostIPs: - ip: 2620:52:0:1308::5 - ip: 192.168.111.5 phase: Running podIP: fd01:0:0:1::4a podIPs: - ip: fd01:0:0:1::4a - ip: 10.132.0.41 qosClass: BestEffort
Expected results:
Pod gets an IPv4 automatically.
Additional info:
I can provide access to a reproducible environment.
Affected Platforms: OCP 4.19
Is it an
- internal RedHat testing failure
If it is an internal RedHat testing failure:
- Ping me on slack @mavazque