Pacemaker start action failed due to container name already in use
Issue
A container in pacemaker cluster failed to start because the container name is already in use by a container ID in the controller, when no container with that name is in running state.
Environment
- Red Hat Openstack Platform 16.2
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
