Bug 1638931

Summary: plan-environment.yaml in home dir can break undercloud install/upgrade
Product: Red Hat OpenStack Reporter: James Slagle <jslagle>
Component: python-tripleoclientAssignee: Emilien Macchi <emacchi>
Status: CLOSED ERRATA QA Contact: Sasha Smolyak <ssmolyak>
Severity: medium Docs Contact:
Priority: medium    
Version: 14.0 (Rocky)CC: bdobreli, emacchi, hbrock, jslagle, mburns
Target Milestone: z1Keywords: Triaged, ZStream
Target Release: 14.0 (Rocky)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-tripleoclient-10.6.1-0.20181010222415.8c8f259.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-18 13:03:10 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 James Slagle 2018-10-12 22:00:34 UTC 
openstack tripleo deploy, which drives the undercloud installer and upgrade, defaults to using plan-environment.yaml from the current directory as set in contsants.py.

This can cause issues when using the openstack undercloud commands if you happen to have a plan-environment.yaml from your overcloud (or from anywhere) in the current directory.

In my case, I had downloaded plan-environment.yaml from swift for my *overcloud* and saved it in my home dir to do some debugging. Later when I went to upgrade my undercloud I started getting errors about missing environments that the undercloud installer was trying to use due to it trying to load non-existing environments from my overcloud plan-environment.yaml.
Comment 3 Mikey Ariel 2019-02-20 12:44:31 UTC 
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text.

If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Comment 5 errata-xmlrpc 2019-03-18 13:03:10 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/RHBA-2019:0446