Looking at the logs from some of the rechecks on this bug this looks like a nova network issue. See:
http://logs.openstack.org/68/43868/1/check/gate-tempest-devstack-vm-postgres-full/37db98a/logs/screen-n-net.txt.gz#_2013-08-27_12_05_34_349
and
http://logs.openstack.org/68/43868/1/check/gate-tempest-devstack-vm-postgres-full/37db98a/logs/screen-n-cpu.txt.gz#_2013-08-27_12_05_34_411
I don't think there will need to be any changes on the tempest side. But, I'll wait until after there is a fix on the nova side.
Also I believe I've seen this error on other tests so I don't think there is anything aggregates specific about it.
Looking at the logs from some of the rechecks on this bug this looks like a nova network issue. See:
http:// logs.openstack. org/68/ 43868/1/ check/gate- tempest- devstack- vm-postgres- full/37db98a/ logs/screen- n-net.txt. gz#_2013- 08-27_12_ 05_34_349
and
http:// logs.openstack. org/68/ 43868/1/ check/gate- tempest- devstack- vm-postgres- full/37db98a/ logs/screen- n-cpu.txt. gz#_2013- 08-27_12_ 05_34_411
I don't think there will need to be any changes on the tempest side. But, I'll wait until after there is a fix on the nova side.
Also I believe I've seen this error on other tests so I don't think there is anything aggregates specific about it.