16c423fa17
Our LBaaSv2 database code was set to delete a pool's session_persistence if the pool was updated and the update API request did not include mention of the session_persistence. Expected behavior would be to not change the session_persistence. In addition, while editing this code it became obvious that we didn't provide a good way to clear the session_persistence for a pool once it was set, especially via the CLI. This has also been corrected. Change-Id: I654b172927e1d96677a7da9e0846231b0ac48aa9 Depends-On: Idcf12e463fbaa3a61a211f13986d8472f52036d2 Closes-Bug: #1552086 Partial-Bug: #1547157
24 lines
787 B
YAML
24 lines
787 B
YAML
---
|
|
issues:
|
|
- |
|
|
CLI update does not allow clearing session_persistence.
|
|
|
|
In the process of fixing the session_persistence
|
|
update bug, we discovered that the CLI for updating
|
|
LBaaS v2 pools does not allow one to clear the
|
|
session_persistence for a pool once set. A fix for
|
|
this is being prepared, but in the mean time, the
|
|
following work-arounds are possible if a given
|
|
pool's session_persistence parameter needs to be
|
|
changed:
|
|
|
|
* The pool can be deleted and recreated without
|
|
session_persistence.
|
|
* A tenant can update the session persistence by
|
|
talking directly to the API using curl.
|
|
fixes:
|
|
- |
|
|
session_persistence on a LBaaSv2 pool is no longer
|
|
deleted when other pool parameters are updated via
|
|
the CLI or API.
|