You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After applying the fix in #1730, to make the 'reboot on raspbian' task actually work (without a fatal error), I realized that this causes another problem: when the ARM servers reboot mid-playbook, the playbook fails. Even if only the master node fails, everything else will fail at the Copy the K3s service file task with the message:
AnsibleUndefinedVariable: 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'token'
To Reproduce
Run the Ansible playbook on ARM servers.
Expected behavior
The playbook completes successfully, and reboots the ARM servers as required in the Rebooting on Raspbian task.
Actual behavior
TASK [raspbian : Rebooting on Raspbian] ********************************************************************************
Saturday 02 May 2020 11:36:06 -0500 (0:00:02.881) 0:00:38.813 **********
skipping: [worker-01]
skipping: [worker-02]
skipping: [worker-03]
skipping: [worker-04]
skipping: [worker-05]
skipping: [worker-06]
fatal: [turing-master]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Shared connection to turing-master closed.", "unreachable": true}
Which, in turn, causes all the other hosts to fail:
TASK [k3s/node : Copy K3s service file] ********************************************************************************
Saturday 02 May 2020 11:36:14 -0500 (0:00:06.435) 0:00:46.844 **********
fatal: [worker-01]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'token'"}
fatal: [worker-02]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'token'"}
fatal: [worker-03]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'token'"}
fatal: [worker-05]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'token'"}
fatal: [worker-04]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'token'"}
fatal: [worker-06]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'token'"}
Additional context / logs
N/A
The text was updated successfully, but these errors were encountered:
Version:
N/A
K3s arguments:
N/A
Describe the bug
After applying the fix in #1730, to make the 'reboot on raspbian' task actually work (without a fatal error), I realized that this causes another problem: when the ARM servers reboot mid-playbook, the playbook fails. Even if only the
master
node fails, everything else will fail at theCopy the K3s service file
task with the message:To Reproduce
Run the Ansible playbook on ARM servers.
Expected behavior
The playbook completes successfully, and reboots the ARM servers as required in the
Rebooting on Raspbian
task.Actual behavior
Which, in turn, causes all the other hosts to fail:
Additional context / logs
N/A
The text was updated successfully, but these errors were encountered: