helpernode run fails with default chrony config
yussufsh opened this issue · 1 comments
yussufsh commented
module.helpernode.null_resource.config (remote-exec): TASK [Create temporary chrony.conf file] ***************************************
module.helpernode.null_resource.config (remote-exec): fatal: [192.168.99.2]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute 'content'"}
Introduced from #56
yussufsh commented
chronyconfig.content is required as per the helpernode playbook with at least 1 entry and that could be the bastion node.