4919bf7213
After the management reconfiguration, it was not possible to apply a reboot-required patch because the sysinv was sending the old mgmt IP adress to the mtce. Consequently, mtce wasn't creating the required file (/var/run/.node_locked) during the host-lock command. This file is essential for the sw-patch tool to proceed with the installation. Additionally, the management network reconfiguration runtime manifest can be executed prematurely if the MGMT_NETWORK_RECONFIGURATION_ONGOING flag is used. However, users might introduce other changes that could unintentionally trigger the runtime manifests before the host-unlock command. This could lead to unexpected keystone changes, potentially causing CLI blockage or system reboots. The MGMT_NETWORK_RECONFIGURATION_ONGOING flag is created when initiating management network reconfiguration commands and it is intended to avoid update on the dnsmasq files until system reboot. Changed to MGMT_NETWORK_RECONFIGURATION_UNLOCK because this flag is intended to guarantee keystone changes only occur during the unlock command. Tests dome: IPv4 AIO-SX fresh install IPv4 AIO-DX with mgmt in vlan fresh install IPv4 DC with subcloud AIO-SX IPv4 AIO-SX mgmt reconfig and apply a reboot-required patch IPv4 subcloud AIO-SX mgmt reconfig and apply a reboot-required patch Partial-Bug: #2060066 Story: 2010722 Task: 49810 Change-Id: I138d8e31edd60a41a4595cfb8bd2dc478bc01013 |
||
|---|---|---|
| .. | ||
| cert-alarm | ||
| cert-mon | ||
| cgts-client | ||
| ipsec-auth | ||
| sysinv | ||
| sysinv-agent | ||