-
Bug
-
Resolution: Done
-
Normal
-
4.9
-
Important
-
None
-
3
-
T&PS 2023 #5, T&PS 2023 #6, T&PS 2023 #7, T&PS 2023 #10
-
4
-
Rejected
-
Unspecified
-
If docs needed, set a value
-
Disclaimer
----------
I'm opening this BZ following a comment from BZ#2058030 (https://bugzilla.redhat.com/show_bug.cgi?id=2058030#c55).
Please reassign to the right component if needed.
Description of problem
----------------------
When trying to deploy a BM-IPI cluster with dual-stack IPv4/IPv6 support, the CSR of the worker nodes are not approved.
Additional info
---------------
The CSR is not approved because the IPv6 address of the node in the CSR doesn't match the IPv6 address in the matching BMH resource.
AFAIK, the clusters affected by this issue use SLAAC for IPv6 address configuration, there is no DHCPv6 server.
The IPv6 address was not correct in the CSR resource because the configuration was done using stable-privacy mode instead of eui64 mode. This is fixed by this change in configure-ovs script: https://github.com/openshift/machine-config-operator/pull/3024.
The remaining issue is the IPv6 address in the BMH resource not being the same probably because it's configured using stable-privacy mode instead of eui64 mode in the IPA environment.
Version
-------
This issue has been reproduced using OCP 4.9 and 4.11 nightlies.
Note that, currently I can test only using 4.11 nightlies because of some regressions in configure-ovs script for OCP 4.9 and OCP 4.10 (see BZ#1929160 and BZ#2058030).
- links to