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.
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 -.
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