yahoo-eng-team team mailing list archive

[Ann Taraday <akamyshnikova@xxxxxxxxxxxx>]

*** This bug is a duplicate of bug 1649503 ***
    https://bugs.launchpad.net/bugs/1649503

I debug this issue today. 
Here are some logs http://paste.openstack.org/show/609902/

And it shows the following result:
qos_policy_id for network is not getting updated, so need_network_update_notify is False https://github.com/openstack/neutron/blob/master/neutron/plugins/ml2/plugin.py#L856 - http://paste.openstack.org/show/609903/, some more http://paste.openstack.org/show/609907/ - get_network gets stale info.

So, it seems I hit https://bugs.launchpad.net/neutron/+bug/1649503. So,
we need to backport this one.


** This bug has been marked a duplicate of bug 1649503
   Mechanism driver getting stale QoS data on network update

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1688538

Title:
  [SR-IOV] --no-qos-policy for network does not clean applied limits for
  ports

Status in neutron:
  New

Bug description:
  When remove qos-policy from network limits on SR-IOV ports are not cleared - http://paste.openstack.org/show/608964/ . There are no errors in logs.
  If we launch another new port in this network no qos rule will apply to it, but existing one can be cleared only manually.
  If the same qos policy applied for the port directly with --no-qos-policy it is cleared.

  Reproduced on the stable/newton.

  Ubuntu 16.04.
  Ethernet controller: Intel Corporation 82599ES 10-Gigabit
  Kernel driver in use: ixgbe

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1688538/+subscriptions