[QoS] QoS policy doesn't update rule after recreating net,route,instance and applying existing rule

Detailed bug description:

When I create router, net, VMs, policy and bandwidth rule and applying it on port - it is works correctly. But, when VMs, router, net was deleted and recreated - after applying policy on new just created port and updating bandwidth-limit-rule it is have no effect and speed is equal to bandwidth that was before updating.

Steps to reproduce:

1. neutron net-create net01
2. neutron subnet-create net01 192.168.112.0/24 --name subnet01
3. neutron router-create router01
4. neutron router-interface-add router01 subnet01
5. neutron router-interface-add router01 admin_floating_net__subnet
6. Net_ID=`neutron net-list | grep net01 | awk '{print $2}'`

7. nova boot --flavor m1.medium --image Ubuntu_14.04_iperf_nload --availability-zone nova:node- 2.domain.tld --key-name CloudKey --nic net-id=$Net_ID Ubuntu-1

8. nova boot --flavor m1.medium --image Ubuntu_14.04_iperf_nload --availability-zone nova:node-3.domain.tld --key-name CloudKey --nic net-id=$Net_ID Ubuntu-2

9. neutron qos-policy-create bwlimiter
10. neutron qos-bandwidth-limit-rule-create bwlimiter --max-kbps 13000
11. Find Ubuntu-1 port
12. Update this port with qos-policy bwlimiter
13. Start iperf server on Ubuntu-2
14. Start iperf client on Ubuntu-1
15. Look at the traffic on Ubuntu-1. It is eq qos-policy bwlimiter
16. nova delete Ubuntu-1
17. nova delete Ubuntu-2
18. neutron router-interface-delete router01 subnet01
19. neutron router-interface-delete router01 admin_floating_net__subnet
20. neutron net-delete net01
21. repeat steps 1-8
22. Find Ubuntu-1 port
24. Update this port with qos-policy bwlimiter
25. Start iperf server on Ubuntu-2
26. Start iperf client on Ubuntu-1
27. Look at the traffic on Ubuntu-1.
28. bandwidth-limit-rule ID=`neutron qos-bandwidth-limit-rule-list bwlimiter | grep 13000 | awk '{print $2}'`
29. Update bandwidth-limit-rule. neutron qos-bandwidth-limit-rule-update $ID bwlimiter --max-kbps 20000
30. Look at the traffic on Ubuntu-1. It is not changed and equal 13000 instead of 20000

Expected results:
Traffic restriction must be equal bandwidth-limit-rule (20000 kbps)

Actual result:
Traffic restriction equal bandwidth-limit-rule that was created befor deleting router,net,VMs (13000 kbps)

Additional information:

There is some logs from /var/log/neutron/neutron-openvswitch-agent.log on node-2 after updating bandwidth-limit-rule

http://paste.openstack.org/show/496886/

Description of the environment:

fuel_build_id | 308 |

fuel_build_number | 308 |

fuel_release | 9.0 |

fuel_openstack_version | mitaka-9.0 |

Diagnostic snapshot - http://mos-scale-share.mirantis.com/fuel-snapshot-2016-05-11_19-00-11.tar.xz