Bug 1242989

Summary:	Allow run "overcloud node delete" 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:	augol, calfonso, jslagle, mburns, ohochman, rbiba, 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 openstack-tripleo-heat-templates-0.8.6-39.el7ost	Doc Type:	Enhancement
Doc Text:	This release allow the use of Heat templates directly when deleting overcloud nodes. You can now run the "openstack overcloud node delete" command with the "--templates" parameter if the overcloud was deployed without Tuskar.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:59:23 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 14:11:09 UTC

Description of problem:
"openstack overcloud node delete" currently works only with tuskar. It should allow to use heat templates directly same as "openstack overcloud deploy" command.

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

Comment 3 Jan Provaznik 2015-07-15 14:39:52 UTC

upstream patches:
https://review.openstack.org/#/c/202054/
https://review.gerrithub.io/#/c/239944/

Comment 4 Jan Provaznik 2015-07-15 14:58:06 UTC

Also this upstream patch for THT is needed:
https://review.openstack.org/#/c/199576/

Comment 7 errata-xmlrpc 2015-08-05 13:59:23 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