It seems that if there is a 'delete traversal' and a resource is locked for updating metadata from a scaling activity, it just bails out with 'resource is locked for update; deferring'[1], then nothing happens(no re-triggering) and the stack gets stuck in DELETE_IN_PROGRESS.
We can probably fix the test by waiting for 'metadata['scaling_in_progress'] to be False. But that would not be the right solution.
It seems that if there is a 'delete traversal' and a resource is locked for updating metadata from a scaling activity, it just bails out with 'resource is locked for update; deferring'[1], then nothing happens(no re-triggering) and the stack gets stuck in DELETE_IN_PROGRESS.
We can probably fix the test by waiting for 'metadata[ 'scaling_ in_progress' ] to be False. But that would not be the right solution.
[1] http:// logs.openstack. org/40/ 374440/ 3/check/ gate-heat- dsvm-functional -convg- mysql-lbaasv2/ 2149180/ logs/screen- h-eng.txt. gz#_2016- 09-22_05_ 18_23_228