networking-odl dynamic port status update full support missing

Bug #1686023 reported by Josh Hershberg
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-odl
In Progress
Low
Unassigned

Bug Description

With these [1] patches merged networking_odl will support dynamically updating the port status at port bind time from DOWN to ACTIVE. In order to avoid a race condition when the websocket reconnects and networking-odl is forced to pull port statuses in separate (REST) calls, it was decided to only support updating the port status at bind time and from DOWN->ACTIVE.

Especially missing is port status transitions resulting from admin state UP/DOWN. Networking-odl needs to be fixed so that it can handle any change of port status reported by ODL.

[1]
https://review.openstack.org/#/c/421127/
https://review.openstack.org/#/c/444047/
https://review.openstack.org/#/c/453563/
https://git.opendaylight.org/gerrit/#/c/51554/
https://git.opendaylight.org/gerrit/#/c/55854/
https://git.opendaylight.org/gerrit/#/c/55856/

Changed in networking-odl:
importance: Undecided → High
status: New → In Progress
Revision history for this message
Isaku Yamahata (yamahata) wrote :

Now DOWN to ACTIVE is supported.
The remaining issue is admin_state_up=DOWN case.
For now there isn't strong requirement to support admin_state_up except tesmpest testcase,
making this low priority.

Changed in networking-odl:
importance: High → Low
Revision history for this message
Matt Riedemann (mriedem) wrote :

Is this fixed since https://review.openstack.org/#/c/465463/ is merged?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.