98be6376b2
When manila services are stopped or restarted via stop(), the DB entries are not deleted, they are destroyed only in kill() method. In cluster deployments, where multiple instances of manila services are deployed via PODs, unique hostname is derived from node name. However if pods are deployed again and launched on new hosts/nodes, the old entries of manila service remains as it is. Fix it by adding 'state' column in 'services' table and introducing per service cleanup function. On service stop, state is changed to 'stopped' and cleanup function will delete 'stopped' services unless they are 'up' again before cleanup periodic interval. Closes-bug: #1990839 Change-Id: I8b71c4c27ff8fcb25616a95a5ed8362a7f4ffc61
12 lines
633 B
YAML
12 lines
633 B
YAML
---
|
|
fixes:
|
|
- |
|
|
In cluster deployments, where multiple instances of manila services are
|
|
deployed via PODs, unique hostname is derived from node name. However if
|
|
pods are deployed again and launched on new hosts/nodes, the old entries
|
|
of manila service remains as it is. Fixed it by adding per service cleanup
|
|
function and also introducing 'state' column in 'services' table. The
|
|
service will be in either of 'up', 'down' or 'stopped' state. Cleanup will
|
|
delete DB entries of 'stopeed' services. For more details please refer,
|
|
`Launchpad bug 1990839 <https://bugs.launchpad.net/manila/+bug/1990839>`_
|