ansible replay fails if kubeadm init was not successful
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
David Sullivan |
Bug Description
Brief Description
-----------------
If the first attempt to run the ansible playbook fails to complete kubeadm init, subsequent runs will always fail.
Severity
--------
Critical
Steps to Reproduce
------------------
Bring up the system and run the ansible bootstrap playbook with a unified docker registry that is invalid/not reachable from the host
The playbook will fail (this is expected) - the error should look like this:
Some fatal errors occurred:\n\t[ERROR ImagePull]: failed to pull image 10.10.10.
Remove the invalid docker registry and rerun the bootstrap playbook
Expected Behavior
------------------
The ansible playbook should complete.
Actual Behavior
----------------
The ansible playbook fails with the following error:
[kubelet-check] It seems like the kubelet isn't running or healthy
Reproducibility
---------------
100%
System Configuration
-------
All configurations
Branch/Pull Time/Commit
-------
20190728T233000Z
Last Pass
---------
I believe this passed with 20190707T233000Z
Timestamp/Logs
--------------
NA
Test Activity
-------------
Developer Testing
Changed in starlingx: | |
status: | In Progress → Fix Released |
tags: | added: in-r-stx20 |
I used the following data for localhost.yml to induce the first error in vbox
external_ oam_subnet: 10.10.10.0/24 oam_gateway_ address: 10.10.10.1 oam_floating_ address: 10.10.10.2 become_ pass: Li69nux*
external_
external_
management_subnet: 192.168.204.0/24
dns_servers:
- 8.8.4.4
admin_password: Li69nux*
ansible_
docker_registries:
unified: 10.10.10.13:5000