Comment 2 for bug 1915856
Revision history for this message
| Balazs Gibizer (balazs-gibizer) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Hm the two reproduction of the bug seems to be different regarding step 3) and the allocation key in the port binding.
In the first reproduction there is no way to have an allocation key as nova never set one in the first place during the boot of the VM as at that time there was no resource request of the port. At step 3) the new qos policy is accepted by neutron and the resource request is updated but no allocation.
While in the second reproduction case there is an allocation key set originally by nova at boot time as at that time there was a port resource request. When the qos policy is then removed from the port neutron updated the resource request and deleted the allocation from placement, but kept the allocation key in the port binding. Then at step 4) when the qos policy is set again on the port neutron accepted the new qos policy but did _not_ update the resource request of the port and did not update the placement allocation either.