Docker container deletion should be intolerant to the fact if the container is present or not
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Undecided
|
Jeff Peeler |
Bug Description
When deleting container and the container failed to get started previously it is is impossible to properly delete it, most of other resources should be intolerant to that fact.
IRC log:
[15:38:20] <shardy> chmouel: can you expand on the requirement? For delete you should just be able to re-try the delete until you fix the error and it works
[15:38:55] <chmouel> shardy: well as an example I am trying out the docker container which failed to start for some reason
[15:39:11] <chmouel> shardy: if i want to try to delete it would just say cannot delete since it doesn't exist
[15:39:27] <chmouel> shardy: is it by design or it needs a fix in the docker client ?
[15:39:38] <shardy> chmouel: that's a bug, most resources tolerate NotFound exceptions and treat it as a successful delete
Changed in heat: | |
assignee: | nobody → Chmouel Boudjnah (chmouel) |
Changed in heat: | |
assignee: | Chmouel Boudjnah (chmouel) → Jeff Peeler (jpeeler-z) |
status: | New → In Progress |
Changed in heat: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | juno-3 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/113371
Review: https:/