Looks like the instance booting block on acquire lock on COMPUTE_RESOURCE_SEMAPHORE?
The instance stop after:
http://logs.openstack.org/39/404239/14/check/gate-tempest-dsvm-ironic-ipa-wholedisk-pxe_snmp-tinyipa-ubuntu-xenial-nv/8f98498/logs/screen-n-cpu.txt.gz#_2016-12-21_13_24_24_327
Then periodic task update_available_resource always get the lock:
release the lock http://logs.openstack.org/39/404239/14/check/gate-tempest-dsvm-ironic-ipa-wholedisk-pxe_snmp-tinyipa-ubuntu-xenial-nv/8f98498/logs/screen-n-cpu.txt.gz#_2016-12-21_13_24_24_367
Then acquire lock soon http://logs.openstack.org/39/404239/14/check/gate-tempest-dsvm-ironic-ipa-wholedisk-pxe_snmp-tinyipa-ubuntu-xenial-nv/8f98498/logs/screen-n-cpu.txt.gz#_2016-12-21_13_24_24_370
I don't know why update_available_resource always run, there should be 60 seconds interval?
Looks like the instance booting block on acquire lock on COMPUTE_ RESOURCE_ SEMAPHORE?
The instance stop after:
http:// logs.openstack. org/39/ 404239/ 14/check/ gate-tempest- dsvm-ironic- ipa-wholedisk- pxe_snmp- tinyipa- ubuntu- xenial- nv/8f98498/ logs/screen- n-cpu.txt. gz#_2016- 12-21_13_ 24_24_327
Then periodic task update_ available_ resource always get the lock:
release the lock http:// logs.openstack. org/39/ 404239/ 14/check/ gate-tempest- dsvm-ironic- ipa-wholedisk- pxe_snmp- tinyipa- ubuntu- xenial- nv/8f98498/ logs/screen- n-cpu.txt. gz#_2016- 12-21_13_ 24_24_367
Then acquire lock soon http:// logs.openstack. org/39/ 404239/ 14/check/ gate-tempest- dsvm-ironic- ipa-wholedisk- pxe_snmp- tinyipa- ubuntu- xenial- nv/8f98498/ logs/screen- n-cpu.txt. gz#_2016- 12-21_13_ 24_24_370
I don't know why update_ available_ resource always run, there should be 60 seconds interval?