My previous comment referencing bug 1185834 only applied to comment #2.
AFAICT the originally reported bug is indeed unique. There is no KeyError reported in the compute log of that one and the state of the instance is BUILD, not ERROR as in the case of bug 1185834.
If one follows the failing spawn request (req-1cec748a-a4ec-42f6-a877-864605a1d688) it looks like it never finishes, no trace or anything unusual other than the request id never shows up in the log again after this final row:
My previous comment referencing bug 1185834 only applied to comment #2.
AFAICT the originally reported bug is indeed unique. There is no KeyError reported in the compute log of that one and the state of the instance is BUILD, not ERROR as in the case of bug 1185834.
If one follows the failing spawn request (req-1cec748a- a4ec-42f6- a877-864605a1d6 88) it looks like it never finishes, no trace or anything unusual other than the request id never shows up in the log again after this final row:
2013-05-17 22:41:06.500 DEBUG nova.openstack. common. processutils [req-1cec748a- a4ec-42f6- a877-864605a1d6 88 demo demo] Running cmd (subprocess): sudo nova-rootwrap /etc/nova/ rootwrap. conf qemu-nbd -c /dev/nbd3 /opt/stack/ data/nova/ instances/ 87c1dc14- 44b1-406f- a7a0-c41876dc91 11/disk execute /opt/stack/ new/nova/ nova/openstack/ common/ processutils. py:142