Bug 1242990

Summary:	Allow extra env files when running "overcloud node delete"
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	Doc Type:	Enhancement
Doc Text:	New in this release is the ability to accept extra Heat environment files when deleting a node from overcloud. When using an isolated network, extra environment files must be passed to Heat on any overcloud update. With this update, the "openstack overcloud node delete" command can be used to delete overcloud nodes on an isolated network.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:59:26 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:13:04 UTC

Description of problem:
"openstack overcloud node delete" currently doesn't support passing heat extra environment files. Because network isolation config is passed in these extra env files to "openstack overcloud deploy" and have to be passed on any stack-update operation too, we need to support when deleting a node too.

Comment 3 Jan Provaznik 2015-07-15 14:41:27 UTC

upstream patches:
https://review.openstack.org/#/c/202055/
https://review.gerrithub.io/#/c/239945/

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