Reviewed: https://review.openstack.org/126903 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6e79981b7caadbbbb2119461034dfe7b4d1c1a64 Submitter: Jenkins Branch: proposed/juno
commit 6e79981b7caadbbbb2119461034dfe7b4d1c1a64 Author: Derek Higgins <[email protected]> Date: Fri Sep 12 16:31:44 2014 +0100 Retry getting the list of service plugins On systems that start both neutron-server and neutron-l3-agent together, there is a chance that the first call to neutron will timeout. Retry upto 4 more times to avoid the l3 agent exiting on startup. This should make the l3 agent a little more robust on startup but still not ideal, ideally it wouldn't exit and retry periodically. Change-Id: I2171a164f3f77bccd89895d73c1c8d67f7190488 Closes-Bug: #1353953 Closes-Bug: #1368152 Closes-Bug: #1368795 (cherry picked from commit e7f0b56d74fbfbb08a3b7a0d2da4cefb6fe2aa67) ** Changed in: neutron Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1368152 Title: l3 agent dies after MessagingTimeout error Status in OpenStack Neutron (virtual network service): Fix Released Bug description: l3 agent dies after MessagingTimeout error, attached is the trace. I am not sure about the root cause of the MessagingTimeout either but that seems a different problem, I think agent should survive the timeout and retry maybe. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1368152/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
