yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #59004
[Bug 1642476] Re: Associating qos can't bump port/network revision number
Reviewed: https://review.openstack.org/398827
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=0e51574b2fb299eb42d6f5333e68f70244b08d50
Submitter: Jenkins
Branch: master
commit 0e51574b2fb299eb42d6f5333e68f70244b08d50
Author: Hong Hui Xiao <honghui_xiao@xxxxxxxx>
Date: Thu Nov 17 14:24:05 2016 +0800
Have qos object increment port/network revision
When associate/disassociate qos of port/network, port/network's revision
number will not bump. This patch fixes that.
Change-Id: I1e60851fb1e99a3f803e0bf3854653ff107f768f
Closes-Bug: #1642476
** Changed in: neutron
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1642476
Title:
Associating qos can't bump port/network revision number
Status in neutron:
Fix Released
Bug description:
When associate/disassociate qos with port/network, the port/network's
revision number will not change.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1642476/+subscriptions
References