Bug 1471700 - port status upate: missing add of provisioning component
Summary: port status upate: missing add of provisioning component
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-odl
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Upstream M3
: 12.0 (Pike)
Assignee: Josh Hershberg
QA Contact: Itzik Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-17 09:30 UTC by Itzik Brown
Modified: 2018-10-18 07:25 UTC (History)
3 users (show)

Fixed In Version: python-networking-odl-11.0.0-0.20170719125820.14ee893.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
N/A
Last Closed: 2017-12-13 21:42:20 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1704057 0 None None None 2017-07-17 09:30:07 UTC
OpenStack gerrit 483199 0 None None None 2017-07-23 12:36:04 UTC
Red Hat Product Errata RHEA-2017:3462 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 12.0 Enhancement Advisory 2018-02-16 01:43:25 UTC

Description Itzik Brown 2017-07-17 09:30:07 UTC
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:

Comment 2 Itzik Brown 2017-08-16 08:24:38 UTC
Josh,
Can you please suggest verification steps?

Thanks

Comment 3 Itzik Brown 2017-09-14 08:51:50 UTC
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

Comment 6 errata-xmlrpc 2017-12-13 21:42:20 UTC
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

Comment 8 Josh Hershberg 2018-04-02 13:51:53 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.