Comment 5 for bug 1831664

Reviewed: https://review.opendev.org/665353
Committed: https://git.openstack.org/cgit/starlingx/config/commit/?id=9568d970f174349aab9b17dcd1673b13aa9ebce2
Submitter: Zuul
Branch: master

commit 9568d970f174349aab9b17dcd1673b13aa9ebce2
Author: Tee Ngo <email address hidden>
Date: Thu Jun 13 22:46:03 2019 -0400

    Add pods wait time to initial bootstrap play

    In latest loads that have kernel update among other code
    changes to various StarlingX repos, it is observed that
    not all kube-system pods get started before the host
    becomes online whereas they consistently did in the same
    slow lab in an older load. As a result, the bootstrap
    playbook often fails in this slow lab toward the end where
    it verifies kube-system pods readiness.

    This commit is a follow-up of commit
    97181aa756854800d40db3f6099ec31541b47a88. In this commit, a
    30 second pause is applied to initial play to ensure all
    pods have been started before executing the task that waits
    for them to become ready. The total wait time for replay
    remains unchanged at 60 seconds.

    Tests:
      Play and replay the bootstrap playbook locally on slow
      hardware.

    Closes-Bug: 1831664
    Change-Id: I525c7771eafad2b9e79dd89e985696fb16bb5b24
    Signed-off-by: Tee Ngo <email address hidden>