https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/NETVIRT-1178 netvirt <p>After rebooting a compute node the OVS is connected to the all the controllers but the pseudo agent is down.</p> <p>In Neutron log:<br/> 2018-03-27 07:31:09.202 34 WARNING neutron.db.agents_db <span class="error">&#91;req-86b57593-85d6-4c20-bba1-d408151e94ef - - - - -&#93;</span> Agent healthcheck: found 1 dead agents out of 11:<br/>                 Type       Last heartbeat host<br/>               ODL L2  2018-03-27 07:05:06 compute-0.localdomain</p> <p>Version:<br/> opendaylight-8.0.0-3.el7ost.noarch</p> NETVIRT-1178

ODL L2 Agent is dead after restarting a compute node

Bug High Resolved Done Josh Hershberg Itzik Brown Tue, 27 Mar 2018 07:49:36 +0000 Wed, 23 May 2018 10:08:09 +0000 Wed, 23 May 2018 10:08:09 +0000 General 0 2 <p>The second karaf.log is with OVSDB Trace</p> <p>Root cause:</p> <p>When an ovsdb client connects a component, StalePassiveConnectionService, checks to see if there are any previous connections to that same client. If there are, they are pinged to determine whether or not they are still actually connected. The callback that handles the ping results does not fire properly in the event of a timeout and the onFailure method does not call OvsdbConnectionService.notifyListenerForPassiveConnection for the new connection. This results in the new connection not being being reported "up the stack." </p> <p><a href="https://git.opendaylight.org/gerrit/#/c/71203/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/71203/</a></p> Relates OVSDB-444 Development Rank 0|i03ccn: