1. The stack_status did not changed to "UPDATE_IN_PROGRESS" immediately when executed "heat stack-update"
stack@dixiaoli-heat-devstack-2:~$ heat stack-update -f resource-group-stack.yaml -P flavor=m1.small stack_01
+--------------------------------------+------------+-----------------+---------------------+--------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+-----------------+---------------------+--------------+
| 6a9ee7b4-b58e-413a-83c2-5683b32a7b7c | stack_01 | CREATE_COMPLETE | 2015-10-26T05:09:09 | None |
+--------------------------------------+------------+-----------------+---------------------+--------------+
stack@dixiaoli-heat-devstack-2:~$ heat stack-list
+--------------------------------------+------------+--------------------+---------------------+---------------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+--------------------+---------------------+---------------------+
| 6a9ee7b4-b58e-413a-83c2-5683b32a7b7c | stack_01 | UPDATE_IN_PROGRESS | 2015-10-26T05:09:09 | 2015-10-26T05:10:35 |
+--------------------------------------+------------+--------------------+---------------------+---------------------+
2.The stack_status did not changed to "DELETE_IN_PROGRESS" immediately when executed "heat stack-delete"
stack@dixiaoli-heat-devstack-2:~$ heat stack-delete stack_01
+--------------------------------------+------------+-----------------+---------------------+---------------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+-----------------+---------------------+---------------------+
| f00b65be-e9c9-48d2-a275-e9c663649124 | stack_01 | UPDATE_COMPLETE | 2015-10-26T05:18:11 | 2015-10-26T05:19:17 |
+--------------------------------------+------------+-----------------+---------------------+---------------------+
stack@dixiaoli-heat-devstack-2:~$ heat stack-list
+--------------------------------------+------------+--------------------+---------------------+---------------------+
| id | stack_name | stack_status | creation_time | updated_time |
+--------------------------------------+------------+--------------------+---------------------+---------------------+
| f00b65be-e9c9-48d2-a275-e9c663649124 | stack_01 | DELETE_IN_PROGRESS | 2015-10-26T05:18:11 | 2015-10-26T05:19:17 |
+--------------------------------------+------------+--------------------+---------------------+---------------------+
This is expected, both those calls are asynchronous, and as such the API call starts the operation and the status gets updated after the call completes.
The bug really is that the API doesn't consistently return 202 (accepted) for all asynchronous operations, which is a known issue and something we're planning to fix if/when we create a v2 API:
https:/
https:/