Bug 1844792

Summary:	[OSP] Floating IP specified with lbFloatingIP in install-config.yaml fails to attach to master node causing install to fail
Product:	OpenShift Container Platform	Reporter:	Anil Dhingra <adhingra>
Component:	Installer	Assignee:	Eric Duen <eduen>
Installer sub component:	OpenShift on OpenStack	QA Contact:	David Sanz <dsanzmor>
Status:	CLOSED DUPLICATE	Docs Contact:
Severity:	high
Priority:	high	CC:	pprinett, talayan
Version:	4.5
Target Milestone:	---
Target Release:	---
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:	2020-06-08 16:14:55 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 Anil Dhingra 2020-06-07 08:18:12 UTC

Description of problem:

During the openshift on openstack install process a floating IP is being attached to the bootstrap node. It's failing to attach the floating IP specified in install-config.yml to the api node

Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
ansible --version

How reproducible:

Steps to Reproduce:
1. Deploy OSP
2. Run openshift-install

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Anil Dhingra 2020-06-07 08:24:35 UTC

opened this as previous bug https://bugzilla.redhat.com/show_bug.cgi?id=1734460 was closed without resolution .

this issue has  very negative impact on CNV-2.4 testing. We need to get this issue solved instead applying some workaround.

Comment 2 Tareq Alayan 2020-06-07 09:23:22 UTC

Happens on OPENSHIFT_INSTALLER_VERSION=4.5.0-rc.1
rhcos: rhcos-45.81.202005200134-0

Comment 3 Pierre Prinetti 2020-06-08 16:14:55 UTC


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