A docker resource fails to stop if the container does not exist but another object of the same name exists
Issue
ocf:heartbeat:docker
resource fails to stop even though the managed container has already been removed.- A
docker
resource fails to stop when the image and container share the same name.
Environment
- Red Hat Enterprise Linux 7 (with the High Availability Add-on)
- An
ocf:heartbeat:docker
resource resource-agents
package versions prior to4.1.1-12.el7
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.