Comment 8 for bug 1662109

Looking at the logs of the agent here:

http://logs.openstack.org/07/436307/1/check/gate-tempest-dsvm-neutron-dvr-multinode-scenario-ubuntu-xenial-nv/342948d/logs/screen-q-agt.txt.gz

I can see updates to the specific port (a5b6388d-6d1a-41d7-aa21-4cf65c5abcd) but nothing related to the QoS policy: 9be9a9a5-ba61-4ae5-ae28-689edd so, it seems like we have a genuine bug, where somehow the agent is not getting the qos_policy_id on the port when the port is updated.

So the question is, what is preventing such port update from reaching the agent via RPC properly... I'll keep looking at this.