No container status constant for 'Unknown'
Bug #1489996 reported by
Ryan Rossiter
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
Undecided
|
Ryan Rossiter |
Bug Description
It looks like when an exception gets raised when getting the containers, the API is setting the status of the container to be 'Unknown'. (see https:/
'Unknown' is not defined in https:/
Changed in magnum: | |
assignee: | nobody → Ryan Rossiter (rlrossit) |
Changed in magnum: | |
milestone: | none → mitaka-1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/218415 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=cac328d1c43 1f61bb81ea607d3 5859599b7ac6b5
Committed: https:/
Submitter: Jenkins
Branch: master
commit cac328d1c431f61 bb81ea607d35859 599b7ac6b5
Author: Ryan Rossiter <email address hidden>
Date: Fri Aug 28 18:39:19 2015 +0000
Add UNKNOWN constant to container statuses
The container API would set the status of a container to 'Unknown' if
there was an exception when retrieving the container. This status should
be contained as a constant (as with all other container constants). This
change adds an UNKNOWN constant to the container object module, and
changes the API to use that constant instead of the hard-coded string.
Change-Id: I7cec02e2e8b861 9bd2fcba4ba867e c8b21ad5afe
Closes-Bug: #1489996