Don't create new QoS policy during update operation
The QoS plugin erroneously creates a new policy when updating
an existing one.
This causes the loss of previously set attributes that are
not passed in the update call.
This patch fixes this issue by getting existing qos policy object
instead of creating a new one for update.
This issue is already fixed in Pike branch with patch:
I57011bd4d40479855203061554090d19bb668960
Reviewed: https:/ /review. openstack. org/523133 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=29aafaf5f98 2e9df794ef54a9e fb54fa758d7432
Committed: https:/
Submitter: Zuul
Branch: stable/ocata
commit 29aafaf5f982e9d f794ef54a9efb54 fa758d7432
Author: Sławek Kapłoński <email address hidden>
Date: Mon Nov 27 14:29:58 2017 +0000
Don't create new QoS policy during update operation
The QoS plugin erroneously creates a new policy when updating
an existing one.
This causes the loss of previously set attributes that are
not passed in the update call.
This patch fixes this issue by getting existing qos policy object
instead of creating a new one for update.
This issue is already fixed in Pike branch with patch: 047985520306155 4090d19bb668960
I57011bd4d4
Change-Id: I6f5a925084bb70 b56e66d673eac2f ebdb38e0b34
Related-Bug: #1734136