Hide Forgot
Description of problem: Although the initial patches for port status update trigger the provisioning block when the port transitions to active, it did not actually add the provisioning block first. This caused occasional failures in the gates. The reason this did not always fail was because of a race condition with dhcp where dhcp was setting the port status in time. Version-Release number of selected component (if applicable): python-networking-odl-11.0.0-0.20170710194836.ba60ac7.el7ost.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Josh, Can you please suggest verification steps? Thanks
Verified that the port starts in a 'DOWN' state and moves to 'ACTIVE' Also in the Neutron server log: 2017-09-14 08:47:45.023 101400 DEBUG networking_odl.ml2.port_status_update [req-d27d2449-15e4-4a9c-b269-5676c7261502 - - - - -] Update port for port id 015d2d80-8af9-4f15-b160-e59902fc4cbc DOWN _process_websocket_recv /usr/lib/python2.7/site-packages/networking_odl/ml2/port_status_update.py:87 2017-09-14 08:47:54.601 101400 DEBUG networking_odl.ml2.port_status_update [req-d27d2449-15e4-4a9c-b269-5676c7261502 - - - - -] Update port for port id 015d2d80-8af9-4f15-b160-e59902fc4cbc ACTIVE _process_websocket_recv /usr/lib/python2.7/site-packages/networking_odl/ml2/port_status_update.py:87 Version ======== opendaylight-6.1.0-2.el7ost.noarch python-networking-odl-11.0.1-0.20170831202719.81010b8.el7ost.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462
1) Kill the dhcp agent 2) spin a VM 3) check the logs to see that ODL reported the port is ACTIVE 4) check that neutron does not report the port as ACTIVE. If this is indeed the case, than this is verified.