Comment 1 for bug 2029375

Reviewed: https://review.opendev.org/c/starlingx/vault-armada-app/+/890256
Committed: https://opendev.org/starlingx/vault-armada-app/commit/896008fb732dc1d1541564da109275a753b6e65c
Submitter: "Zuul (22348)"
Branch: master

commit 896008fb732dc1d1541564da109275a753b6e65c
Author: Tae Park <email address hidden>
Date: Tue Aug 1 17:29:01 2023 -0400

    vault-manager wait for one server only when initialized

    Modifying the vault-manager initialization logic so that it only waits
    for pod number equal to the replica value to be active
    if the raft is not yet initialized.

    TEST PLAN:
     - In a 2 controller, 1 worker setup,
     - Upload and apply vault
     - Lock the host that vault-manager is running on
     - Vault manager should restart
     - Within the logs, there should not be a repetition of " Waiting for sva-vault statefulset running pods..."
     - Vault Sanity test in AIO-SX
     - Bashate of rendered init.sh

    Closes-bug: 2029375

    Signed-off-by: Tae Park <email address hidden>
    Change-Id: I41990b87395a5d5364ef91c048f740d0f0675d6b