-
Bug
-
Resolution: Done
-
Major
-
4.12.0
-
None
-
Critical
-
None
-
SDN Sprint 232, SDN Sprint 233
-
2
-
Rejected
-
False
-
Description of problem:
After IPI installing a 3-node Hub Cluster, and converting them to dual stack, fd69::/125 address is seen in the Baremetal br-ex interface
Version-Release number of selected component (if applicable):
4.12.0
How reproducible:
Ranodmly reproduced and this IP is assigned in one of the 3 master hub cluster nodes
Steps to Reproduce:
1. IPI install 4.12.0 2. Use the Convert from IPv4/IPv6 dual stack procedure. 3.
Actual results:
Check for the IP fd69::/125 in the br-ex interface
OVN CrashLoopBackOff
Expected results:
The IP is a internal OVNKUBE IP, and it should not appear on the interface.
fd69::2/125 should be present on br-ex, but make sure fd69::2 does not :
- show up as an address in the node Status.Addresses list at all
- exist in any Node object annotations
Additional info:
This is one of the issues in IPv6 that is discovered, the other issue is linked here as well.
- clones
-
OCPBUGS-6504 IPI Baremetal Master Node in DualStack getting fd69:: address randomly, OVN CrashLoopBackOff
- Closed
- is blocked by
-
OCPBUGS-6504 IPI Baremetal Master Node in DualStack getting fd69:: address randomly, OVN CrashLoopBackOff
- Closed
- relates to
-
OCPBUGS-12799 OCP 4.12.x Upgrade Failure: OVN-KUBE-POD Crashes
- Closed
- links to