I spent some time poking around and I find the NoValidHost exception is no longer exposed, so the failures to schedule stay silent. The only log of the error shows as a warning in the conductor log as Exception is caught and logged in this way:
2014-06-10 00:42:10.968 WARNING nova.scheduler.driver [req-247b18f2-2163-482b-8fd0-4f04193521b8 AttachInterfacesTestXML-245370658 AttachInterfacesTestXML-1095742173] [instance: e7c227f7-5eb2-4ec4-ba6a-1dcb833aa85e] Setting instance to ERROR state.
http://logs.openstack.org/64/98564/3/check/check-tempest-dsvm-neutron/9941781/logs/screen-n-cond.txt.gz?level=TRACE
I spent some time poking around and I find the NoValidHost exception is no longer exposed, so the failures to schedule stay silent. The only log of the error shows as a warning in the conductor log as Exception is caught and logged in this way:
2014-06-10 00:42:10.968 WARNING nova.scheduler. driver [req-247b18f2- 2163-482b- 8fd0-4f04193521 b8 AttachInterface sTestXML- 245370658 AttachInterface sTestXML- 1095742173] [instance: e7c227f7- 5eb2-4ec4- ba6a-1dcb833aa8 5e] Setting instance to ERROR state.
http:// logs.openstack. org/64/ 98564/3/ check/check- tempest- dsvm-neutron/ 9941781/ logs/screen- n-cond. txt.gz? level=TRACE