From the very beginning (06036fd6dba3ba4b9a13052ea95a08ebcc97501e), the
action apply was ignoring the passed --managed-by values and was always
taking defaults ('paunch').
Fix this and provide no upgrade/update impact, which is for whatever
--managed-by value given to paunch, perform all checks and searches
also for that historically "wrong" value 'paunch':
* if a container needs to be (re)started by a new 'managed-by', make sure
it can be found by the default 'paunch' value as well, then reset its
managed-by to the desired value.
Reviewed: https:/ /review. opendev. org/696675 /git.openstack. org/cgit/ openstack/ paunch/ commit/ ?id=965e3cfecb5 d20bf1929adbe3f 5ef5adc069705f
Committed: https:/
Submitter: Zuul
Branch: stable/rocky
commit 965e3cfecb5d20b f1929adbe3f5ef5 adc069705f
Author: Bogdan Dobrelya <email address hidden>
Date: Thu Nov 28 15:31:55 2019 +0100
Fix action Apply ignoring managed-by arg
From the very beginning (06036fd6dba3ba 4b9a13052ea95a0 8ebcc97501e) , the
action apply was ignoring the passed --managed-by values and was always
taking defaults ('paunch').
Fix this and provide no upgrade/update impact, which is for whatever
--managed-by value given to paunch, perform all checks and searches
also for that historically "wrong" value 'paunch':
* if a container needs to be (re)started by a new 'managed-by', make sure
it can be found by the default 'paunch' value as well, then reset its
managed-by to the desired value.
Closes-bug: #1853812
Change-Id: If129bbc1ff3294 1d06ff480f26870 b10840591e0 33b8b71a21fe24b 241ecb639b)
Signed-off-by: Bogdan Dobrelya <email address hidden>
(cherry picked from commit 12ccf36b0e7f9b2