'compute-0' is in disabled state after install due to an ipsec-client error

[Manoel Benedito Neto]

Brief Description
-----------------
'compute-0' is in disabled state and offline after lab install. Even after delete it and applied the DM again.

Severity
-----------------
Major

Steps to Reproduce
------------------
System Install.

Expected Behavior
-----------------
compute-0 should be online and available state.

Actual Behavior
---------------
sysadmin@controller-0:~$ kubectl get hosts -n=deployment -o=wide
NAME ADMINISTRATIVE OPERATIONAL AVAILABILITY PROFILE INSYNC SCOPE RECONCILED
compute-0 unlocked enabled available compute-0-profile true bootstrap true
controller-0 unlocked enabled available controller-0-profile true bootstrap true
controller-1 unlocked enabled degraded controller-1-profile true bootstrap true

Reproducibility
---------------
100% reproducible

System Configuration
--------------------
Multi-node system

Last Pass
---------
N/A

Timestamp/Logs
--------------
2024-05-20T18:28:30.252057776Z INFO controller.host waiting for host monitor to trigger another reconciliation {"request": "deployment/compute-0"}
2024-05-20T18:28:30.255062698Z INFO host-resource default {"name": "compute-0"}
2024-05-20T18:28:30.270811268Z INFO host-resource default {"name": "compute-0"}
2024-05-20T18:28:30.273230084Z INFO host-resource validate update {"name": "compute-0"}
2024-05-20T18:28:30.273241902Z INFO host-resource allowed to be admitted
2024-05-20T18:28:31.221978686Z INFO controller.host.deployment/compute-0 Sync interface name
2024-05-20T18:28:31.222124981Z INFO controller.host waiting for host monitor to trigger another reconciliation {"request": "deployment/compute-0"}

Test Activity
-------------
Sanity

Workaround
----------
N/A

[Ghada Khalil (gkhalil)]

Issue is related to IPSec enablement on the mgmt network: https://storyboard.openstack.org/#!/story/2010940

[Ghada Khalil (gkhalil)]

Fixed by: https://review.opendev.org/c/starlingx/config/+/922016
Merged on June 18.