I'm not sure if this bug is actually the right place to track all of these, since the problem doesn't really seem to be that the upgrade failed, and just that smoke tests failed against the original deploy (best I can tell) - but I suppose each of these initial test failures is actually going to have it's own root cause for the real failure.
Another instance of the initial smoke tests failing during a grenade upgrade:
http:// logs.openstack. org/32/ 91732/2/ check/check- grenade- dsvm/0caa773/ logs/new/
The ER fingerprint identified this failure as https:/ /bugs.launchpad .net/tempest/ +bug/1253896
... but it actually looks more like https:/ /bugs.launchpad .net/nova/ +bug/1254890
http:// logs.openstack. org/32/ 91732/2/ check/check- grenade- dsvm/0caa773/ console. html#_2014- 05-08_08_ 26_00_767
I'm not sure if this bug is actually the right place to track all of these, since the problem doesn't really seem to be that the upgrade failed, and just that smoke tests failed against the original deploy (best I can tell) - but I suppose each of these initial test failures is actually going to have it's own root cause for the real failure.
Which *may* be a libvirt issue?
http:// logs.openstack. org/32/ 91732/2/ check/check- grenade- dsvm/0caa773/ logs/libvirtd. txt.gz# _2014-05- 08_08_25_ 58_098
http:// logs.openstack. org/32/ 91732/2/ check/check- grenade- dsvm/0caa773/ logs/old/ screen- n-cpu.txt. gz?#_2014- 05-08_08_ 25_59_240