Comment 2 for bug 2039863

Reviewed: https://review.opendev.org/c/starlingx/ansible-playbooks/+/899303
Committed: https://opendev.org/starlingx/ansible-playbooks/commit/948c93ae7355daf17633304a56bcc11bf4fffc86
Submitter: "Zuul (22348)"
Branch: master

commit 948c93ae7355daf17633304a56bcc11bf4fffc86
Author: Igor Soares <email address hidden>
Date: Wed Oct 25 16:06:48 2023 -0300

    Mark config as incomplete when shutting down k8s

    Delete /etc/platform/.initial_k8s_config_complete file to signal that
    configuration is incomplete when shutting down Kubernetes during
    bootstrap replays.

    The bootstrap playbook creates the
    /etc/platform/.initial_k8s_config_complete file when bringing Kubernetes
    up. This file, however, was not being removed when bringing it down
    during replays which, in turn, was preventing bootstrap from succeeding.

    Deleting service parameters during bootstrap replays relies on the
    .initial_k8s_config_complete file to tell whether configmaps should be
    deleted. If the file is not removed then the service parameter delete
    function mistakenly considers that Kubernetes is running when it is not,
    thus causing a failure when attempting to delete configmaps.

    Test Plan:
    PASS: build-pkgs -a && build-image
    PASS: AIO-SX full deployment without bootstrap replay
    PASS: AIO-SX full deployment with bootstrap replay
    PASS: Install AIO-SX load
          Add apiserver_extra_args:default-not-ready-toleration-seconds
          to localhost.yml
          Run boostrap playbook
          Replay boostrap playbook
          Run 'system service-parameter-list' and check if
          default-not-ready-toleration-seconds is listed
          Check if default-not-ready-toleration-seconds was added to
          kube-apiserver parameters
          Unlock node

    Closes-Bug: 2039863

    Change-Id: I29f7cc1766cb8c218908bfb1c130b0a8507a9965
    Signed-off-by: Igor Soares <email address hidden>