Container create failed on docker but still saved in magnum

Bug #1449872 reported by Lan Qi song
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Magnum
Invalid
Undecided
Lan Qi song

Bug Description

When container create failed (such as we create a container has a same name with an already exist container):

$magnum container-create < cirros-container.json
ERROR: Docker API Error : 409 Client Error: Conflict ("Conflict, The name test-container is already assigned to 158af4981e18ef621d0df7a70e4b19128da4a3deb05d6c0a77915fccc02c2105. You have to delete (or rename) that container to be able to assign test-container to a container again.") (HTTP 500)

Actually, it was already created in magnum:
$ magnum container-list
+--------------------------------------+-----------------+
| uuid | name |
+--------------------------------------+-----------------+
| 47d187bd-4fd4-46f7-941e-1a493eddcd52 | test-container |
| 7e4700bd-02b7-48cb-b46e-33d88acf3a88 | test-container |
+--------------------------------------+-----------------+

And we can't figure out which one is the success one.

Revision history for this message
Lan Qi song (lqslan) wrote :
Changed in magnum:
assignee: nobody → Lan Qi song (lqslan)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on magnum (master)

Change abandoned by Lan Qi Song (<email address hidden>) on branch: master
Review: https://review.openstack.org/178523

Adrian Otto (aotto)
Changed in magnum:
milestone: none → mitaka-1
Changed in magnum:
status: In Progress → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.