Tee Ngo 9568d970f1 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 97181aa756. 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 <tee.ngo@windriver.com>		2019-06-14 06:45:26 -04:00
..
apply-bootstrap-manifest	Remove misleading debug task	2019-05-28 11:53:15 -04:00
bringup-essential-services	Add pods wait time to initial bootstrap play	2019-06-14 06:45:26 -04:00
persist-config	Remove the is_kubernetes checks from sysinv	2019-06-07 16:49:42 -05:00
prepare-env	Add pods wait time to initial bootstrap play	2019-06-14 06:45:26 -04:00
store-passwd	Ansible Bootstrap Deployment	2019-04-11 08:40:34 -04:00
validate-config	add registry.local as a default no_proxy url.	2019-06-04 11:30:23 +08:00