During scale tests we saw that neutron agent aliveness mechanism is not working properly and was marking agents as down and thus failing on port binding. We assessed that aliveness in our context is not actually interesting, as we only use the agentdb mechanism to store the information we need for port binding. As a result of this assessment we decided to remove the aliveness awareness from the code and try to bind the port disregarding that. The consequence of this is that a "neutron agent-list" call might show the agent as dead or alive but that's not information we should depend on to understand if we are binding to that node. This needs to be clear, specially because the aliveness mechanism was added as a result of a bug [1] and there might be expectations for it to work according to the alive status on agentdb. [1] https://bugs.launchpad.net/networking-odl/+bug/1712334
As per depreciation notice [1], closing this bug. Please reopen if relevant for RHOSP13, as this is the only version shipping ODL. [1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/14/html-single/release_notes/index#deprecated_functionality