Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1737150

Summary: Add addtional checks to undercloud deploy for admin_vip and admin_host IP's
Product: Red Hat OpenStack Reporter: bjacot
Component: python-tripleoclientAssignee: Alex Schultz <aschultz>
Status: CLOSED ERRATA QA Contact: bjacot
Severity: medium Docs Contact:
Priority: medium    
Version: 15.0 (Stein)CC: aschultz, emacchi, hbrock, jschluet, jslagle, mburns
Target Milestone: asyncKeywords: Triaged, ZStream
Target Release: 15.0 (Stein)   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: python-tripleoclient-11.5.1-0.20190910010428.885c409.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-05 11:59:15 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 bjacot 2019-08-02 20:16:39 UTC
Additional checks are needed in the undercloud deploy.  When a customer is deploying UC with an ip subnet NOT 192.168.24.x the undercloud.conf must have IP's for the undercloud_admin_vip and public vip.  If not connections cant be made between the front end and backend to the database.  It will cause the deployment to hang and the install not to succeed.

To prevent these issues this needs to be set in the undercloud.conf: 
undercloud_admin_host = {any unsued addresses on the ctlplane network}
undercloud_public_host = {any unsued addresses on the ctlplane network}
undercloud_public_vip = {any unsued addresses on the ctlplane network}
undercloud_admin_vip = {any unsued addresses on the ctlplane network}

Example:
local_ip = 192.168.220.1/24
undercloud_admin_host = 192.168.220.3
undercloud_public_host = 192.168.220.2
undercloud_public_vip = 192.168.220.2
undercloud_admin_vip = 192.168.220.3

Debug session:
keystone db sync blocks the deployment because it cannot connect to the mysql frontend defined for haproxy with a wrong IP address:

[stack@core-undercloud-0 ~]$ ip -4 -o a
1: lo    inet 127.0.0.1/8 scope host lo\       valid_lft forever preferred_lft forever
3: eth1    inet 172.16.220.50/24 brd 172.16.220.255 scope global dynamic noprefixroute eth1\       valid_lft 2552sec preferred_lft 2552sec                                       
4: eth2    inet 10.0.220.61/24 brd 10.0.220.255 scope global dynamic noprefixroute eth2\       valid_lft 2556sec preferred_lft 2556sec                                           
6: br-ctlplane    inet 192.168.220.1/24 brd 192.168.220.255 scope global br-ctlplane\       valid_lft forever preferred_lft forever  

listen mysql
  bind 192.168.24.3:3306 transparent
  timeout client 90m
  timeout server 90m
  server core-undercloud-0.ctlplane.localdomain 192.168.220.1:3306 backup check fall 5 inter 2000 rise 2

To prevent these issues this needs to be set in the undercloud.conf: 
undercloud_admin_host = {any unsued addresses on the ctlplane network}
undercloud_public_host = {any unsued addresses on the ctlplane network}
undercloud_public_vip = {any unsued addresses on the ctlplane network}
undercloud_admin_vip = {any unsued addresses on the ctlplane network}

Example:
local_ip = 192.168.220.1/24
undercloud_admin_host = 192.168.220.3
undercloud_public_host = 192.168.220.2
undercloud_public_vip = 192.168.220.2
undercloud_admin_vip = 192.168.220.3

Comment 3 Alex Schultz 2019-08-28 17:16:39 UTC
*** Bug 1737153 has been marked as a duplicate of this bug. ***

Comment 6 errata-xmlrpc 2020-03-05 11:59:15 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, 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-2020:0643