Bug 1809664

Summary: IPv6 Master machines are not assigned to nodes
Product: OpenShift Container Platform Reporter: Amit Ugol <augol>
Component: InstallerAssignee: Stephen Benjamin <stbenjam>
Installer sub component: OpenShift on Bare Metal IPI QA Contact: Amit Ugol <augol>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: high CC: augol, cvultur, jtomasek, kni-bugs, mcornea, rbryant, rhhi-next-mgmt-qe, sgordon, stbenjam, wsun
Version: 4.4Keywords: TestBlocker
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1801238 Environment:
Last Closed: 2020-03-18 16:59:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1801238, 1840106, 1840133    
Bug Blocks: 1771572, 1801970    

Description Amit Ugol 2020-03-03 16:15:34 UTC
+++ 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).

--- Additional comment from Stephen Benjamin on 2020-02-24 14:40:09 UTC ---

Moving this to 4.5. To get this change in 4.4 at this point, you'll need to fix it in 4.5, and clone this bug to 4.4.

--- Additional comment from Wei Sun on 2020-02-25 05:10:03 UTC ---

Hi, per #comment4, if it needs to be fixed in 4.4, please clone one bug for 4.4.

--- Additional comment from Russell Bryant on 2020-02-27 17:37:24 UTC ---

This is expected behavior right now with bare metal IPI.  It can be worked around with an external script that writes Addresses to the master Machines.  dev-scripts used to have a script to do this.

AFAIK, the functional impact of this issue is that it breaks some of the bare metal host management in the UI.

--- Additional comment from Marius Cornea on 2020-02-27 19:01:45 UTC ---



--- Additional comment from Marius Cornea on 2020-02-27 19:02:10 UTC ---



--- Additional comment from Marius Cornea on 2020-02-27 19:02:29 UTC ---



--- Additional comment from Marius Cornea on 2020-02-27 19:05:03 UTC ---

Workaround:

download add-machine-ips.sh link-machine-and-node.sh utils.sh scripts in the same directory

export KUBECONFIG=clusterconfigs/auth/kubeconfig 
export CLUSTER_NAME=ocp-edge-cluster
bash add-machine-ips.sh

--- Additional comment from Marius Cornea on 2020-02-27 19:09:15 UTC ---

Also jq needs to be installed on the machine where the workaround steps are run.

--- Additional comment from Marius Cornea on 2020-02-27 20:47:45 UTC ---

Also need to set link-machine-and-node.sh as executable

chmod +x link-machine-and-node.sh

Comment 1 Stephen Benjamin 2020-03-18 16:59:18 UTC
BZ1801238 is tracking this in 4.5.  Closing this one.

*** This bug has been marked as a duplicate of bug 1801238 ***