Details
-
Bug
-
Resolution: Done
-
Normal
-
4.11
-
Moderate
-
Unspecified
-
If docs needed, set a value
Description
Description of problem:
When deploying OCP using ipv6 static IP configuration on baremetal network, worker nodes fail to create.
The cluster-machine-approver doesn't approve the csr because it's expecting the name openshift-worker-0-0, whereas the actual node name is worker-0-0.ocp-edge-cluster-0.qe.lab.redhat.com (this name is picked up by backwards dns lookup)
Similar configuration is successful when run on ipv4.
Version-Release number of selected component (if applicable):
4.11.0-0.nightly-2022-07-08-231743
How reproducible: 2/2
Steps to Reproduce:
Deploy OCP with networkConfig section for each of the nodes, similar to the following:
networkConfig:
routes:
config:
- destination: ::/0
next-hop-address: fd2e:6f44:5dd8::1
next-hop-interface: enp0s4
dns-resolver:
config:
server: - fd2e:6f44:5dd8::1
interfaces: - name: enp0s4
type: ethernet
state: up
ipv6:
address: - ip: fd2e:6f44:5dd8::56
prefix-length: 64
enabled: true
Actual results:
Deployment fails because worker nodes aren't created
Expected results:
Deployment succeeds
Additional info:
Must-gather: http://rhos-compute-node-10.lab.eng.rdu2.redhat.com/logs/must-gather.local.240973992141636803.tar.gz
install-config.yaml: http://rhos-compute-node-10.lab.eng.rdu2.redhat.com/logs/install-config.static.ipv6.yaml