Public bug reported: Deployment using OVS as network backend. QoS enabled.
During the port deletion, the QoS OVS agent extension removes the possible QoS rules applied on a port (max BW egress/ingress, min BW egress/ingress). During this process, in "delete_ingress_bw_limit_for_port", the port is checked and then, if exists, it is modified to delete the QoS reference (clear "qos" column in "port" DB register). As seen in [1], the port can be deleted between both operations (retrieval, modification), resulting in an error. [1]http://paste.openstack.org/show/795047/ ** Affects: neutron Importance: Undecided Assignee: Rodolfo Alonso (rodolfo-alonso-hernandez) Status: In Progress -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1884512 Title: [QoS] Race condition during port qos rules deletion Status in neutron: In Progress Bug description: Deployment using OVS as network backend. QoS enabled. During the port deletion, the QoS OVS agent extension removes the possible QoS rules applied on a port (max BW egress/ingress, min BW egress/ingress). During this process, in "delete_ingress_bw_limit_for_port", the port is checked and then, if exists, it is modified to delete the QoS reference (clear "qos" column in "port" DB register). As seen in [1], the port can be deleted between both operations (retrieval, modification), resulting in an error. [1]http://paste.openstack.org/show/795047/ To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1884512/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
