Bay status is still CREATE_IN_PROGRESS after bay create failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Invalid
|
Undecided
|
Unassigned |
Bug Description
magnum bay-list
+------
| uuid | name | node_count | master_count | status |
+------
| ca581172-
+------
after 5 minutes it shows
magnum bay-list
+------
| uuid | name | node_count | master_count | status |
+------
| ca581172-
+------
heat stack-list
+------
| id | stack_name | stack_status | creation_time |
+------
| 97d7acc4-
+------
run magnum bay-show test it shows
+------
| Property | Value |
+------
| status | CREATE_FAILED |
| uuid | ca581172-
| status_reason | Resource CREATE failed: Conflict: resources.
| created_at | 2015-09-
| updated_at | 2015-09-
| bay_create_timeout | 0 |
| api_address | None |
| baymodel_id | 94180ed3-
| node_count | 1 |
| node_addresses | [] |
| master_count | 1 |
| discovery_url | https:/
| name | test |
Changed in magnum: | |
milestone: | none → mitaka-1 |
@Gavin, from bug description, I see the status field shows 'CREATE_FAILED' as expected after the creation failed in 'magnum bay-list', 'magnum bay-show' and 'heat stack-list' cmds output. So I believe magnum was working well.