I enabled kube-vip solely with the recent PR; however, I receive errors for my nodes and not my masters

[romelBen]

I recently merged my PR that was submitted in this PR. Everything is running correctly but I came across the end of the ansible setup which gives me this error for my nodes specifically:

TASK [k3s_agent : Enable and check K3s service] ******************************************************************************************
fatal: [192.168.30.80]: FAILED! => {"changed": false, "msg": "Error loading unit file 'k3s-node': org.freedesktop.systemd1.BadUnitSetting \"Unit k3s-node.service has a bad unit file setting.\""}
fatal: [192.168.30.30]: FAILED! => {"changed": false, "msg": "Error loading unit file 'k3s-node': org.freedesktop.systemd1.BadUnitSetting \"Unit k3s-node.service has a bad unit file setting.\""}
fatal: [192.168.3.190]: FAILED! => {"changed": false, "msg": "Error loading unit file 'k3s-node': org.freedesktop.systemd1.BadUnitSetting \"Unit k3s-node.service has a bad unit file setting.\""}

What could this mean?

Currently I have 4 raspberry pis being my masters and my nodes being 3 Dell Optiplex Micro PCs. So 4 arm64 and 3 amd64 PCs. Was wondering with the kube-vip change that this caused me issues.

If you need more info please let me know.

[romelBen]

Disregard. The error was fixed by creating a different k3s_token since the previous cluster had characters that interfered with syncing the node agents to the master cluster. Hope this helps anyone who runs into this issue at the end.