Error deploying overcloud after tripleo-common update

[Rhys Oxenham]

I updated the local packages on my undercloud system, restarted all OpenStack (and supporting) services, and attempted a deployment, and received the following error:

[stack@undercloud ~]$ openstack overcloud deploy --stack region-one --templates --ntp-server x.x.x.x --control-flavor control --compute-flavor compute --control-scale 1 --compute-scale 0 -e ~/multi-site/all-in-one.yaml -e ~/multi-site/region-one.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml --neutron-network-type vxlan --neutron-tunnel-type vxlan --neutron-bridge-mappings datacentre:br-ex
Removing the current plan files
Uploading new plan files
Started Mistral Workflow. Execution ID: 6c367338-32b0-44d3-a472-74e15655ce94
Exception updating plan: Failed to run action [action_ex_id=6f88d00e-8e11-46ba-8d89-4fa547283c67, action_cls='<class 'mistral.actions.action_factory.GeneratePasswordsAction'>', attributes='{}', params='{u'container': u'region-one'}']
 Environment not found [name=tripleo.undercloud-config]

It seems that I didn't re-run 'openstack undercloud install', nor refreshed my Mistral actions/environments and therefore I ran into this issue. So this is more user-error, but the error message could perhaps be handled a little better to point the user in the right direction where possible.

Thanks

[Steven Hardy (shardy)]

Agreed, it'd be good to output a message saying please ensure you ran undercloud install, as unless you have knowledge of the code this error isn't all that helpful.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE