Show status reason for container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Zun |
Fix Released
|
High
|
Pradeep Kumar Singh |
Bug Description
As an operation, I would like to know the container's status and reason, but ....
2016-08-18 07:18:32.147 ERROR zun.compute.manager [req-f19034a3-
2016-08-18 07:18:32.147 TRACE zun.compute.manager File "/opt/stack/
2016-08-18 07:18:32.147 TRACE zun.compute.manager container = self.driver.
2016-08-18 07:18:32.147 TRACE zun.compute.manager File "/opt/stack/
2016-08-18 07:18:32.147 TRACE zun.compute.manager response = docker.
2016-08-18 07:18:32.147 TRACE zun.compute.manager File "/usr/local/
2016-08-18 07:18:32.147 TRACE zun.compute.manager return self.create_
2016-08-18 07:18:32.147 TRACE zun.compute.manager File "/usr/local/
2016-08-18 07:18:32.147 TRACE zun.compute.manager return self._result(res, True)
2016-08-18 07:18:32.147 TRACE zun.compute.manager File "/usr/local/
2016-08-18 07:18:32.147 TRACE zun.compute.manager self._raise_
2016-08-18 07:18:32.147 TRACE zun.compute.manager File "/usr/local/
2016-08-18 07:18:32.147 TRACE zun.compute.manager raise errors.APIError(e, response, explanation=
2016-08-18 07:18:32.147 TRACE zun.compute.manager APIError: 409 Client Error: Conflict ("Conflict. The name "/test" is already in use by container a3e7998d064edd4
ubuntu@
+------
| Property | Value |
+------
| status | Error |
| uuid | 62aa813f-
| links | ["{u'href': u'http://
| image | cirros:latest |
| environment | {} |
| command | sleep 10000 |
| memory | None |
| task_state | None |
| name | test |
+------
See Magnum's implementation as a reference: https:/
Changed in zun: | |
status: | New → Confirmed |
tags: | added: api |
Changed in zun: | |
assignee: | nobody → Arun Dhiman (arundhiman86) |
Changed in zun: | |
status: | Confirmed → Triaged |
description: | updated |
Changed in zun: | |
assignee: | Arun Dhiman (arundhiman86) → bharaththiruveedula (bharath-ves) |
Changed in zun: | |
assignee: | bharaththiruveedula (bharath-ves) → Pradeep Kumar Singh (pradeep-singh-u) |
Yes, need a 'status_reason' field at container.