When using the playbook/role new-linode.yml the user needs to specify the -K or --ask-become-pass in order for the new-linode_create.yml part of the role to modify configurations on localmachine AND also later on for the new-linode_harden.yml role part to finish configuring the newly created linode. The issue is that you only specify the become password at the beginning, which needs to match the localmachine AND the become password for the user that is used to log into the machine and "harden". The script thus breaks if the new-linode user's password does not match the localmachine user's become password
When using the playbook/role new-linode.yml the user needs to specify the -K or --ask-become-pass in order for the new-linode_create.yml part of the role to modify configurations on localmachine AND also later on for the new-linode_harden.yml role part to finish configuring the newly created linode. The issue is that you only specify the become password at the beginning, which needs to match the localmachine AND the become password for the user that is used to log into the machine and "harden". The script thus breaks if the new-linode user's password does not match the localmachine user's become password