Comment 5 for bug 1353953

Revision history for this message
Ben Nemec (bnemec) wrote : Re: guest instance ping timeout on overcloud (Upstream CI failure)

Okay, on a run where neutron-l3-agent doesn't end up dead, os-collect-config ran twice. The first time it started l3-agent it died, but the second time it started successfully: http://logs.openstack.org/74/100374/3/check-tripleo/check-tripleo-novabm-overcloud-f20-nonha/95605a2/logs/overcloud-controller0_logs/os-collect-config.txt.gz

On a bad run, o-c-c only runs once and l3-agent remains dead: http://logs.openstack.org/69/111369/6/check-tripleo/check-tripleo-novabm-overcloud-f20-nonha/772ef25/logs/overcloud-controller0_logs/os-collect-config.txt.gz

Maybe a race with rabbitmq or one of the other neutron services that it seems to be trying to talk to?