e0c45ce4d2
Load balancers were going in to ERROR when updating vip_qos_policy_id in
two different cases:
- QoS extension enabled: the VIP DB data model was incorrectly
constructed ('vip_qos_policy_id' where it should have been
'qos_policy_id')
- QoS extension disabled: setting an UUID or None would fail in the LB
update flow as the extension is disabled, and the API would return
HTTP 202 to the user.
Story: 2004602
Task: 28512
Change-Id: Ie974afa52fe70cbab72b7e7f75bf7ee1015e148c
8 lines
375 B
YAML
8 lines
375 B
YAML
---
|
|
fixes:
|
|
- Fixed an issue where trying to set a QoS policy on a VIP while the QoS
|
|
extension is disabled would bring the load balancer to ERROR. Should the
|
|
QoS extension be disabled, the API will now return HTTP 400 to the user.
|
|
- Fixed an issue where setting a QoS policy on the VIP would bring the load
|
|
balancer to ERROR when the QoS extension is enabled.
|