Bug 1471700 – port status upate: missing add of provisioning component

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1471700 - port status upate: missing add of provisioning component

Summary:	port status upate: missing add of provisioning component

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat OpenStack
Classification:	Red Hat
Component:	python-networking-odl (Show other bugs)
Sub Component:
Version:	12.0 (Pike)
Hardware:	Unspecified Unspecified

Priority	high Severity high
Target Milestone:	Upstream M3
Target Release:	12.0 (Pike)
Assigned To:	Josh Hershberg
QA Contact:	Itzik Brown
Docs Contact:

URL:
Whiteboard:
Keywords:	Triaged

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-07-17 05:30 EDT by Itzik Brown
Modified:	2018-10-18 03:25 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:	python-networking-odl-11.0.0-0.20170719125820.14ee893.el7ost
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Environment:	N/A
Last Closed:	2017-12-13 16:42:20 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Launchpad	1704057	None	None	None	2017-07-17 05:30 EDT
OpenStack gerrit	483199	None	None	None	2017-07-23 08:36 EDT
Red Hat Product Errata	RHEA-2017:3462	normal	SHIPPED_LIVE	Red Hat OpenStack Platform 12.0 Enhancement Advisory	2018-02-15 20:43:25 EST

Groups: None (edit)

Description Itzik Brown 2017-07-17 05:30:07 EDT

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 04:24:38 EDT

Josh,
Can you please suggest verification steps?

Thanks

Comment 3 Itzik Brown 2017-09-14 04:51:50 EDT

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 16:42:20 EST

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 09:51:53 EDT

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.