The controller_config init script is updated to symlink swanctl.conf to
the standby controller version of IPsec config file during reboot.
(swanctl_standby.conf). This makes the symlink correct for only one
controller reboot case (eg, active controller forcely reboot, but when
it comes up it will be standby controller). For rare cases such as
active controller reboot while standby controller is locked, the
symlink on the active controller will be corrected by ipsec-config SM
service when both controllers boots up.
Test Plan:
PASS: In a DX system, force reboot active controller by "reboot -f",
during the controller reboot, verify IPsec SAs are established
and puppet manifests are successfully applied. After the
controller boots up, verify it's unlocked|enabled|available, and
stable with no reboot.
PASS: In a DX system, lock standby controller, then force reboot active
controller by "reboot -f", verify that the swanctl.conf points to
the swanct_standby.conf when it boots up, and then it is
corrected to point to swanctl_active.conf by ipsec-config when SM
services start up, also IPsec SAs are established between
controllers. Eventually both controllers are in
unlocked|enabled|available, system is stable with no reboot.
Story: 2010940
Task: 50195
Change-Id: I1e860b4b4f0f75ff2f8bde81d612d70cb80fb312
Signed-off-by: Andy Ning <andy.ning@windriver.com>
bc0602885c