"undercloud upgrade --use-heat" doesn't work for updating containerized undercloud

[Julie Pichon]

Before containerised undercloud, I always used the "undercloud upgrade" command to keep my undercloud up-to-date with the latest packages / upstream changes.

My development workflow looks like this:

1. Set up a new env or VM
2. Follow the instructions at http://tripleo.org/installation/installation.html#installing-the-undercloud (aka "$ openstack undercloud install --use-heat" now).

From then on, if I need to work with the latest changes or keep my undercloud from becoming stale I follow the instructions at http://tripleo.org/installation/installation.html#updating-undercloud-components :

3. $ openstack undercloud upgrade --use-heat
4. Repeat every few days until I get rid of the VM

The documentation on that installation page suggests to me that this command is used to "update" the undercloud components, so it should be used to keep the undercloud up to date and healthy in general, and not used just once per major release.

From a stable release perspective, that's the process I use as well to get the latest fixes applied onto my Newton (OSP10) undercloud, except step 4 is every few weeks/months instead whenever there's a new point release.

Expectations when running "undercloud upgrade":
- End up with an undercloud that has all packages up to date
- Any changes to e.g. mistral workflows are applied correctly (which wouldn't be the case with only yum update, mistral needs a restart / db populate step)
- Ideally any other necessary step is taken care of (e.g. services that need to be stopped first) but I know that hasn't always been the case, especially with Newton.

It seems counter-intuitive to use "undercloud install" multiple times on the same system in order to keep it up to date.

[Emilien Macchi (emilienm)]

https://review.openstack.org/#/c/565521/

[OpenStack Infra (hudson-openstack)]

Change abandoned by Emilien Macchi (<email address hidden>) on branch: master
Review: https://review.openstack.org/565521

[Emilien Macchi (emilienm)]

So this bug will be closed by https://review.openstack.org/#/c/566214 and https://review.openstack.org/#/c/566145/ for information. I'm testing it at this time but I think it'll really close it.