port_update_postcommit doesn't see latest version of object

Bug #1700351 reported by Omer Anson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
In Progress
Undecided
Omer Anson

Bug Description

Dragonflow's ML2 mechanism driver implements port_update_postcommit, and saves the port object (after translation) to its distributed database.

In Dragonflow's tests [1], this object is compared with the object in the Neutron db (specifically the revision_number, which is translated to version on the Dragonflow object)

Currently, this test fails, since the versions are different, even though there were no additional modifications to the port.

[1] https://github.com/openstack/dragonflow/blob/18b89831532e4a5837e5cb61480f275f03d9d363/dragonflow/tests/unit/test_mech_driver.py#L374

Revision history for this message
Omer Anson (omer-anson) wrote :

I suspect this was added by patch https://review.openstack.org/#/c/475646 , which updates the port's revision number.

Changed in neutron:
assignee: nobody → Omer Anson (omer-anson)
Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/476511
Reason: This review is > 3 months without comment and currently blocked by a core reviewer with a -1. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -1 on this review to ensure you address their concerns.

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.