Bug 1242973

Summary: Allow extra env files when running package update
Product: Red Hat OpenStack Reporter: Jan Provaznik <jprovazn>
Component: python-rdomanager-oscpluginAssignee: Jan Provaznik <jprovazn>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: unspecified Docs Contact:
Priority: high    
Version: 7.0 (Kilo)CC: calfonso, dmacpher, jslagle, mburns, ohochman, rhel-osp-director-maint, rrosa, zbitter
Target Milestone: gaKeywords: Triaged
Target Release: Director   
Hardware: Unspecified   
OS: Unspecified   
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:
The director now provides parameters to accept extra Heat environment files when updating packages on Overcloud nodes. Overcloud isolated networks require extra environment files upon creation and subsequent updates. Without the extra environment files, users cannot use "openstack overcloud update stack" on an Overcloud using isolated network. User now use the "-e" parameter with the "openstack overcloud update stack" command to update packages on Overcloud nodes using isolated networks.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:59:21 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:

Description Jan Provaznik 2015-07-14 13:44:53 UTC
Description of problem:
"openstack overcloud update stack" which updates packages on overcloud nodes 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 it in stack update too.

Implemented in these patches:

Comment 4 Ola Pavlenko 2015-07-22 20:36:40 UTC

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