Associating qos can't bump port/network revision number

Bug #1642476 reported by Hong Hui Xiao
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
High
Hong Hui Xiao

Bug Description

When associate/disassociate qos with port/network, the port/network's revision number will not change.

Hong Hui Xiao (xiaohhui)
Changed in neutron:
assignee: nobody → Hong Hui Xiao (xiaohhui)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/398827

Changed in neutron:
status: New → In Progress
Revision history for this message
Victor Morales (electrocucaracha) wrote :

Hong Hui Xiao, Can you provide the release target for this change?

Changed in neutron:
importance: Undecided → High
milestone: none → ocata-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

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 <email address hidden>
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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 10.0.0.0b2

This issue was fixed in the openstack/neutron 10.0.0.0b2 development milestone.

tags: added: neutron-proactive-backport-potential
tags: removed: neutron-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/422006

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/newton)

Reviewed: https://review.openstack.org/422006
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=6cf3ebb42354f5562afb0df1a6d4e32a720f893b
Submitter: Jenkins
Branch: stable/newton

commit 6cf3ebb42354f5562afb0df1a6d4e32a720f893b
Author: Hong Hui Xiao <email address hidden>
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.

    Conflicts:
     neutron/tests/unit/services/revisions/test_revision_plugin.py

    Change-Id: I1e60851fb1e99a3f803e0bf3854653ff107f768f
    Closes-Bug: #1642476
    (cherry picked from commit 0e51574b2fb299eb42d6f5333e68f70244b08d50)

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 9.2.0

This issue was fixed in the openstack/neutron 9.2.0 release.

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.