Bug 1412588

Summary:	Rebase openstack-tripleo-common to 5.4.1
Product:	Red Hat OpenStack	Reporter:	Jon Schlueter <jschluet>
Component:	openstack-tripleo-common	Assignee:	Dougal Matthews <dmatthew>
Status:	CLOSED ERRATA	QA Contact:	Alexander Chuzhoy <sasha>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	10.0 (Newton)	CC:	mburns, slinaber
Target Milestone:	z1	Keywords:	Rebase, Triaged, ZStream
Target Release:	10.0 (Newton)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-common-5.4.1-1.el7ost	Doc Type:	Rebase: Bug Fixes and Enhancements
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-01 14:47:24 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:

Comment 2 Jon Schlueter 2017-01-12 12:06:02 UTC

openstack-tripleo-common-5.4.1-1.el7ost

Comment 7 Jon Schlueter 2017-01-17 20:19:34 UTC

correcting Initial description Rebase openstack-tripleo-common to 5.4.1

This pulls in a handful of changes

a couple of docker related changes.
Readme changes
and Allow ansible inventory to be configurable

Comment 8 Jon Schlueter 2017-01-17 20:26:37 UTC

(In reply to Jon Schlueter from comment #7)
> correcting Initial description Rebase openstack-tripleo-common to 5.4.1
> 
> This pulls in a handful of changes
> 
> a couple of docker related changes.
> Readme changes
> and Allow ansible inventory to be configurable

correction changes are not relevent and trackers were for different component.

Comment 9 Jon Schlueter 2017-01-17 20:34:13 UTC

rebase brings us one net new patch, mentioned in externals, relating to containers.  So this was primarly re-syncing to clean upstream tag.

Comment 10 Alexander Chuzhoy 2017-01-17 20:34:40 UTC

Verified:

Environment:
openstack-tripleo-common-5.4.1-1.el7ost.noarch



Was able to deploy overcloud (and even launch BM instances with ironic in overcloud).

Comment 12 errata-xmlrpc 2017-02-01 14:47:24 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://rhn.redhat.com/errata/RHBA-2017-0234.html