c2e5db4305
Once k8s comes up after the etcd restore, there is a span of time (around 20s) that the pod states have not been updated and are reported as they were at the point in time where the backup was taken. This returns that the ic-nginx-ingress-ingress-nginx-controller-XXX pod is "Ready", but it is not... in several instances during my tests, the pod was restarted 3-10 seconds after the task "Launch Armada with Helm v3" failed due to not being able to call the webhook. The proposed solution is to delete the pod preemptively and wait for it to be recreated and "Ready". TEST PLAN PASS restore on virtual AIO-SX (CentOS) Closes-Bug: #1978899 Signed-off-by: Thiago Brito <thiago.brito@windriver.com> Change-Id: I20bec1fbbf809bfcf5d515ef55c6d47ab968dbf3
stx-ansible-playbooks
StarlingX Bootstrap and Deployment Playbooks
Execution environment
- Unix like OS (recent Linux based distributions, MacOS, Cygwin)
- Python 2.7
Additional Required Packages
The playbooks in this repo have been verified with the following versions of Ansible and StarlingX playbooks dependencies:
- sshpass 1.06
- python2-ptyprocess 0.5
- python2-pexpect 4.6
- python2-netaddr 0.7
ansible2.7.5
Supported StarlingX Releases
The playbooks in this repo are compatible with the following StarlingX releases:
- 20.01
Executing StarlingX Playbooks
Executing Bootstrap Playbook
Please refer to StarlingX Deployment Guides, section
Configuration controller-0 of the respective system
configuration for instructions on how to set up and execute the
bootstrap playbook from another host.