Bay status is still CREATE_IN_PROGRESS after bay create failed

[Gavin]

magnum bay-list
+--------------------------------------+------+------------+--------------+--------------------+
| uuid | name | node_count | master_count | status |
+--------------------------------------+------+------------+--------------+--------------------+
| ca581172-ceb9-45be-a2fc-7dedb234e04c | test | 1 | 1 | CREATE_IN_PROGRESS |
+--------------------------------------+------+------------+--------------+--------------------+

after 5 minutes it shows
 magnum bay-list
+--------------------------------------+------+------------+--------------+---------------+
| uuid | name | node_count | master_count | status |
+--------------------------------------+------+------------+--------------+---------------+
| ca581172-ceb9-45be-a2fc-7dedb234e04c | test | 1 | 1 | CREATE_FAILED |
+--------------------------------------+------+------------+--------------+---------------+
heat stack-list
+--------------------------------------+-------------------+---------------+---------------------+
| id | stack_name | stack_status | creation_time |
+--------------------------------------+-------------------+---------------+---------------------+
| 97d7acc4-efbc-4835-9216-998b89bfb536 | test-jhvd6huy7wme | CREATE_FAILED | 2015-09-08T07:25:41 |
+--------------------------------------+-------------------+---------------+---------------------+

run magnum bay-show test it shows
+--------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+--------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| status | CREATE_FAILED |
| uuid | ca581172-ceb9-45be-a2fc-7dedb234e04c |
| status_reason | Resource CREATE failed: Conflict: resources.kube_masters.resources[0].resources.kube_master: Port 23d3762d-a6d1-4bef-9870-0558139708ba is still in use. (HTTP 409) (Request-ID: req-e8f1bdc4-0d67-4aa8-8294-8865282f5193) |
| created_at | 2015-09-08T07:25:41+00:00 |
| updated_at | 2015-09-08T07:30:37+00:00 |
| bay_create_timeout | 0 |
| api_address | None |
| baymodel_id | 94180ed3-9193-4a73-b7da-36444959c4b8 |
| node_count | 1 |
| node_addresses | [] |
| master_count | 1 |
| discovery_url | https://discovery.etcd.io/028f6151c04ee75bc7618d578863188b |
| name | test |

[Wenzhi Yu (yuywz)]

@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.