Comment 2 for bug 1805410

This happens on redeploys if the existing container was run (but is dead). This seems to be a bug in paunch where the old container is not relaunch or cleaned up so paunch is creating a new container instance that follows the <containername>-<randomchars> pattern. This latter name comes from the paunch code https://github.com/openstack/paunch/blob/master/paunch/runner.py#L98-L104