Bug 1905990

Summary: RHV IPI Install master node takes VIP ip address
Product: OpenShift Container Platform Reporter: Maria Alonso <malonso>
Component: InstallerAssignee: Evgeny Slutsky <eslutsky>
Installer sub component: OpenShift on RHV QA Contact: Guilherme Santos <gdeolive>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: unspecified CC: dougsland, eslutsky, gdeolive, hpopal, lleistne, mburman, mgold
Version: 4.6   
Target Milestone: ---   
Target Release: 4.6.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-17 19:25:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Maria Alonso 2020-12-09 13:24:33 UTC 
Version:

$ openshift-install version
4.6.6

Platform:
 RHV

Please specify:
IPI

What happened?

After installing the cluster on RHV using IPI installation we see that master node IP is configured with one of the VIP ip addresses.

Sometimes this happens at install time, and other times it happens after rebooting master nodes.

master0 ip addresses, the primary ip address is the expected one:

~~~
2: enp3s0    inet 192.168.48.38/24 brd 192.168.48.255 scope global dynamic noprefixroute enp3s0\       valid_lft 83811sec preferred_lft 83811sec
2: enp3s0    inet 192.168.48.6/32 scope global enp3s0\       valid_lft forever preferred_lft forever
2: enp3s0    inet 192.168.48.5/32 scope global enp3s0\       valid_lft forever preferred_lft forever
But we see that node ip is one of the VIP addresses. 
~~~

After 2nd reboot, we see that master0 ip address is the VIP address:
~~~
NAME                STATUS  ROLES   AGE  VERSION          INTERNAL-IP    EXTERNAL-IP  OS-IMAGE                                                      KERNEL-VERSION                CONTAINER-RUNTIME
ocd-kbzfj-master-1  Ready   master  33m  v1.19.0+43983cd  192.168.48.35  <none>       Red Hat Enterprise Linux CoreOS 46.82.202011210620-0 (Ootpa)  4.18.0-193.29.1.el8_2.x86_64  cri-o://1.19.0-25.rhaos4.6.gitf51f94a.el8
ocd-kbzfj-master-0  Ready   master  33m  v1.19.0+43983cd  192.168.48.5   <none>       Red Hat Enterprise Linux CoreOS 46.82.202011210620-0 (Ootpa)  4.18.0-193.29.1.el8_2.x86_64  cri-o://1.19.0-25.rhaos4.6.gitf51f94a.el8
ocd-kbzfj-master-2  Ready   master  33m  v1.19.0+43983cd  192.168.48.36  <none>       Red Hat Enterprise Linux CoreOS 46.82.202011210620-0 (Ootpa)  4.18.0-193.29.1.el8_2.x86_64  cri-o://1.19.0-25.rhaos4.6.gitf51f94a.el8
~~~


How to reproduce it (as minimally and precisely as possible)?

- Openshift 4.6.6 RHV IPI install


Anything else we need to know?
Comment 3 Evgeny Slutsky 2020-12-14 13:34:19 UTC 
solved by https://github.com/openshift/machine-config-operator/pull/2279
Comment 4 Douglas Schilling Landgraf 2021-01-20 17:39:36 UTC 
The bug is on modified. Can we move to ON_QA at this moment?
Comment 5 Michael Burman 2021-01-27 09:26:11 UTC 
Hi Evgeny, please add the target release. Thanks,
Comment 14 errata-xmlrpc 2021-02-17 19:25:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6.17 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:0424