After moving the nova_api_ensure_cell0_database_url from tripleo_step5
to tripleo_step3 we encounter an error where that container could not
be created during update because it was not being deleted.
The reasoning here is that paunch may look for container to destroy
based on container live information while it creates them based of
file configuration. Then moving container at an earlier step is
Here we work around the issue by making sure that this container is
destroyed before reaching the common deploy step task (where paunch is
triggered) in the update tasks (which happen before).
We look for the current live information of the container and if it is
still in step5 then we delete it.
To prevent such thing to happen again we would need to make sure that
those container are ephemeral and get destroyed after being used.