kolla-ansible destroy leaves ceph_mon_config volume in some cases

[Paul Bourke]

If during setup, Ceph gets the chance to create the ceph_mon_config volume, but fails soon after, tools/cleanup-containers will not be able to recognise this volume for removal. This is because by default it checks for running containers with the kolla label, and uses these to remove volumes. But in this case no ceph containers have started yet.

This then leads to the confusing error documented at http://docs.openstack.org/developer/kolla/ceph-guide.html#deploy-fails-with-fetching-ceph-keyrings-no-json-object-could-be-decoded

[Jeffrey Zhang (jeffrey4l)]

we do not add label into volume. and when cleaning containers, remove the volumes he used.

if the volume is create but the container is disappeared. the volume will be not removed.

[Jeffrey Zhang (jeffrey4l)]

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 (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
  Valid example: CONFIRMED FOR: OCATA