| 1 |
--- |
| 2 |
issues: |
| 3 |
- | |
| 4 |
When using the minimim-bandwidth QoS feature due to bug |
| 5 |
https://launchpad.net/bugs/1921150 physical NIC resource providers |
| 6 |
were for some time created with the wrong parent (i.e. the |
| 7 |
hypervisor RP). This is now partially fixed and new resource |
| 8 |
providers are created now with the expected parent (i.e. the agent |
| 9 |
RP). However Placement does not allow re-parenting an already |
| 10 |
existing resource provider, therefore the following Placement |
| 11 |
DB update may be needed after the fix for bug 1921150 is applied: |
| 12 |
neutron/tools/bug-1921150-re-parent-device-rps.sql |
| 13 |
Until all resource providers have the proper parent, neutron-server |
| 14 |
will retry the re-parenting update, which will be rejected every time, |
| 15 |
therefore expect polluted logs and some wasted load on Placement. |
| 16 |
However please note that the bandwidth-aware scheduling is supposed |
| 17 |
to work even with the wrongly parented resource providers. |