In the first reboot after the management network
reconfiguration, the system is still using the
old mgmt IPs until the apply_network_config.sh
and puppet code updates the system.
The sw-patch services starts before or at same
time of these operations and can use the old
MGMT IPs and failed to answer audit requests.
For this reason the sw-patch services must
start just after the controller config is
completed.
Tests:
IPv6 mgmt network reconfig in subcloud AIO-SX
IPv4 mgmt network reconfig in standalone AIO-SX
AIO-DX Fresh install
AIO-SX Fresh install
AIO-SX IPv4 apply patch after mgmt reconfig
AIO-SX IPv4 apply patch-local before bootstrap
Story: 2010722
Task: 49227
Depends-On: https://review.opendev.org/c/starlingx/config/+/902132
Change-Id: I61cbf24574184dafd0e2e7a80363fecdfa99b5a6
Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com>
085d86e4a3