In your example it looks like nova-net didn't start up
** Changed in: nova
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1257626
Title:
Timeout while waiting on RPC response - topic: "network", RPC method:
"allocate_for_instance" info: "<unknown>"
Status in OpenStack Compute (Nova):
Invalid
Bug description:
http://logs.openstack.org/21/59121/6/check/gate-tempest-dsvm-large-
ops/fdd1002/logs/screen-n-cpu.txt.gz?level=TRACE#_2013-12-04_06_20_16_658
2013-12-04 06:20:16.658 21854 ERROR nova.compute.manager [-] Instance failed
network setup after 1 attempt(s)
<...>
2013-12-04 06:20:16.658 21854 TRACE nova.compute.manager Timeout: Timeout
while waiting on RPC response - topic: "network", RPC method:
"allocate_for_instance" info: "<unknown>"
It appears there has been a performance regression and that
gate-tempest-dsvm-large-ops is now failing because of RPC timeouts to
allocate_for_instance
logstash query: message:"nova.compute.manager Timeout: Timeout while waiting
on RPC response - topic: \"network\", RPC method: \"allocate_for_instance\""
There seems to have been a major rise in this bug on December 3rd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1257626/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
