7fef84e36e
During the management network reconfiguration, the system is restarted to controller_config script runs the puppet code and update all services to use the new mgmt IP address. But the sw-patch services start before the controller_config. When they start they get the mgmt_ip using the python socket lib that uses the IP address from the /etc/hosts. But /etc/hosts at that time is not updated yet, so it get the old management network IP. To fix this issue, the sw-patch services will wait for the puppet code to be applied to make sure the /etc/hosts and new management network IPs were installed in the system. Tests done: IPv4 AIO-SX fresh install IPv4 AIO-DX fresh install IPv4 DC with subcloud AIO-SX fresh install IPv4 AIO-SX mgmt reconfig and apply a non-reboot-required patch IPv4 AIO-SX mgmt reconfig and apply a reboot-required patch IPv4 subcloud AIO-SX mgmt reconfig and apply a non-reboot-required patch IPv4 subcloud AIO-SX mgmt reconfig and apply a reboot-required patch For this test the sw-patch was in failed state after the reboot, It happens even without the mgmt reconfig and this fix Partial-Bug: #2060066 Story: 2010722 Task: 49827 Depends-On: https://review.opendev.org/c/starlingx/config/+/914710 Change-Id: Ie544425513ef4fede73b4b55770ad6857cdf7eed Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com> |
||
---|---|---|
.. | ||
bin | ||
cgcs-patch | ||
debian | ||
scripts |