Bug 1242967

Summary:	Allow run package update with heat templates directly (w/o tuskar)
Product:	Red Hat OpenStack	Reporter:	Jan Provaznik <jprovazn>
Component:	python-rdomanager-oscplugin	Assignee:	Jan Provaznik <jprovazn>
Status:	CLOSED ERRATA	QA Contact:	Amit Ugol <augol>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	7.0 (Kilo)	CC:	calfonso, dmacpher, jslagle, mburns, ohochman, rhel-osp-director-maint, rrosa, zbitter
Target Milestone:	ga	Keywords:	Triaged
Target Release:	Director
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-rdomanager-oscplugin-0.0.8-36.el7ost openstack-tripleo-common-0.0.1.dev6-1.git49b57eb.el7ost	Doc Type:	Enhancement
Doc Text:	In addition to using plans stored in its database, the director now also uses Heat template collections to create an Overcloud. This provides a method to use Heat templates directly when running "openstack overcloud stack update" command to update packages on the Overcloud. If you created the Overcloud using a template collection instead of a plan, run "openstack overcloud stack update" command with the "--templates" parameter instead of the "--plan" parameter.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:59:18 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 Jan Provaznik 2015-07-14 13:38:52 UTC

Description of problem:
"openstack overcloud update stack" which updates packages on overcloud nodes currently works only with tuskar. It should allow to use heat templates directly same as "openstack overcloud deploy" command.

Implemented in this patches:
https://review.openstack.org/#/c/201546/
https://review.gerrithub.io/#/c/239839/

Related documentation patch which describes workaround is:
https://bugzilla.redhat.com/show_bug.cgi?id=1235997

Comment 6 errata-xmlrpc 2015-08-05 13:59:18 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/RHEA-2015:1549