port_update_postcommit doesn't see latest version of object
Bug #1700351 reported by
Omer Anson
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_
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.
Changed in neutron: | |
status: | New → In Progress |
To post a comment you must log in.
I suspect this was added by patch https:/ /review. openstack. org/#/c/ 475646 , which updates the port's revision number.