Comment 3 for bug 1131735

Unfortunately yes, we still do experience this.

1. We create stack on machine with heat working on it.
2. We wait ~20 seconds (~ because we've tried with many configurations of this time, from 5s to 60s)
3. We ask for stack data on v1/tenant_id/stacks/some_stack_name/some_stack_id
4. In 5 second period we ask for stack data on v1/tenant_id/stacks/some_stack_name/some_stack_id (the timeout is 60s-120s depending on current settings) until it returns 'CREATE_COMPLETED'
5. If it returned 'CREATE_COMPLETED' we ask for stack data one more time.

Resonse from 3rd point says the stack status is 'CREATE_IN_PROGRESS' which is right, as heat stack-list on the machine says the same thing.

Resonse from 4th/5th point also says the stack status is 'CREATE_IN_PROGRESS' which is not right, as heat stack-list on the machine says 'CREATE_COMPLETED'.
Usually stack is created after about 20seconds, so in 4th point we can request for stack-data even 8-20 times and usually one of them is right.

As I wrote earlier, it happens randomly in ~50% of cases.