4.3.z Clone
+++ This bug was initially created as a clone of Bug #1801238 +++
Description of problem:
After the cluster is deployed, the master machines are not assigned to nodes. Master Nodes don't have machine.openhift.io/machine annotation and the machine does not have status.addresses an status.nodeRef populated. Executing ./12_csr_hack.sh explicitly fixes the problem.
Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2020-02-03-115336-ipv6.1
How reproducible:
Steps to reproduce the behavior, please include all details about the dev-scripts version (git commit SHA), any local variable overrides or other customizations, and whether you're deploying on VMs or Baremetal.
Recent dev-scripts master (34d334f), default config, only NUM_WORKERS and PULL_SECRET set.
Deploy cluster using default 'make' command. Check one of the master machine resources, the status.addresses and status.nodeRef is not populated.
Actual results:
The masters and nodes are not properly displaying information.
The Nodes are not displaying the number of pods
The BMH does not display any information and graphs
Expected results:
The master machines and nodes should reference each other correctly.
Additional info:
--- Additional comment from Constantin Vultur on 2020-02-10 13:50:11 UTC ---
--- Additional comment from Jiri Tomasek on 2020-02-10 14:19:25 UTC ---
Related Github issue: https://github.com/openshift-metal3/dev-scripts/issues/917
--- Additional comment from Marius Cornea on 2020-02-10 14:31:43 UTC ---
The same issue is present on IPV6 environments deployed with the manual IPI installation process(no dev-scripts involved).
The fix for this problem relies on having continuous introspection running, which lets MAO reconcile which node belongs to which BareMetalHost based on IP. We don't expect this work to be able to be backported to 4.3.z.