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

Bug 1614830

Summary:	Undercloud deployment fails, '- push_destination' is missconfigured.
Product:	Red Hat OpenStack	Reporter:	Alexander Chuzhoy <sasha>
Component:	rhosp-director	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Gurenko Alex <agurenko>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	14.0 (Rocky)	CC:	dbecker, mburns, mcornea, morazi
Target Milestone:	ga
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:	2018-08-10 15:45:46 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 Alexander Chuzhoy 2018-08-10 13:59:44 UTC

Undercloud deployment fails,  '- push_destination' is missconfigured.


Environment:
instack-undercloud-9.1.1-0.20180725192534.41d0460.el7ost.noarch
python-tripleoclient-10.3.1-0.20180726104131.80ac3b9.el7ost.noarch
python-tripleoclient-heat-installer-10.3.1-0.20180726104131.80ac3b9.el7ost.noarch


Steps to reproduce:

Running
openstack tripleo container image prepare default --output-env-file /home/stack/containers-prepare-parameter.yaml --local-push-destination


Results in 

- push_destination: localhost:8787

The undercloud then fails - unable to push container images.
If after failure you re-run 'openstack tripleo container image prepare default --output-env-file /home/stack/containers-prepare-parameter.yaml --local-push-destination'
Then you get:
- push_destination: 192.168.24.1:8787

Comment 2 Alexander Chuzhoy 2018-08-10 14:54:42 UTC

w/a is to fix the push_destination, for example to set:

- push_destination: 192.168.24.1:8787


And to run/re-run 'openstack undercloud install'

Comment 3 Marius Cornea 2018-08-10 15:45:46 UTC

We're keeping track of this issue in BZ#1607999(patches that address the issue are attached to that one)

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