but right before the failure I see that there was still something going on with stack not related to delete - Setting metadata for AutoScalingPolicy "scaleup_policy":
So it seems there is some race during delete in convergence engine, not all internal resource actions are stopped before the delete starts. Or, there should be a retry mechanism in these places.
soo, I've got this too. Judging from the logs:
start of stack delete:
http:// logs.openstack. org/96/ 279096/ 3/check/ gate-heat- dsvm-functional -convg- mysql-lbaasv2/ ac1c829/ logs/screen- h-eng.txt. gz#_2016- 06-21_09_ 27_44_071
failure to acquire resource lock:
http:// logs.openstack. org/96/ 279096/ 3/check/ gate-heat- dsvm-functional -convg- mysql-lbaasv2/ ac1c829/ logs/screen- h-eng.txt. gz#_2016- 06-21_09_ 27_44_388
but right before the failure I see that there was still something going on with stack not related to delete - Setting metadata for AutoScalingPolicy "scaleup_policy":
http:// logs.openstack. org/96/ 279096/ 3/check/ gate-heat- dsvm-functional -convg- mysql-lbaasv2/ ac1c829/ logs/screen- h-eng.txt. gz#_2016- 06-21_09_ 27_44_359
So it seems there is some race during delete in convergence engine, not all internal resource actions are stopped before the delete starts. Or, there should be a retry mechanism in these places.