Issues running the automation - function IPRAP and K3S Nodes Job

[RodCSouza]

Hello team,

I'm trying to use the automation, but I've faced two issues:

Looks like that the adjustments made to cover IPV6 causes a issue in the determination of the IP for the parameter "apiserver_endpoint".

My scenario is one environment where there is no DHCP for IPV6, so the implemented use of function "ansible.utils.ipwrap", returns no data and consequently no IP address information, to correct the errors and be able to continue the automation execution, I've commented the lines with this functions in the file ks3s>master>tasks>main.yml (line 163), this solved the step "Configure kubectl cluster to".

But now I'm facing an error in the step node "Enable and check K3s service", the resultant file of the copy from the template "k3s.service.j2", has also the use of the function "ansible.utils.ipwrap", so I've commented that as well, but the main issue on this point is that the file in the node has no values substituting the corresponding variables, resulting into a job error when trying to rump up the service.

The file content is like this:
`
-- The job identifier is 1862 and the job result is failed.
alchemist@k3s2:/etc/systemd/system$ cat k3s-node.service
[Unit]
Description=Lightweight Kubernetes
Documentation=https://k3s.io
After=network-online.target

[Service]
Type=notify
ExecStartPre=-/sbin/modprobe br_netfilter
ExecStartPre=-/sbin/modprobe overlay
ExecStart=/usr/local/bin/k3s agent --server https://{{ apiserver_endpoint }}:6443 --token {{ hostvars[groups['master'][0]]['token'] | default(k3s_token) }} {{ extra_agent_args | default("") }}
`
I'm wondering if there is a need of Defaults folder and main.yml, for the Nodes section, I'm far from a Ansible expert, so it is just a guess.

Would be nice if you could help me with this.

Thanks.

[sleiner]

My scenario is one environment where there is no DHCP for IPV6, so the implemented use of function "ansible.utils.ipwrap", returns no data and consequently no IP address information

It seems to me like you’re conflating a few things here: The ipwrap filter‘s only purpose is wrapping IPv6 addresses (and only IPv6 addresses) in square brackets. So the output of ipwrap does only depend on the input string, not on the network situation (e.g. the existence of a DHCP6 server).

What is the error message that you are gering with the unmodified roles?

[RodCSouza]

From the executing machine:

[sleiner]

Okay... That version of Ansible should support the ipwrap filter (although it is not exactly new 😅). Just to make sure that the filter is not somehow broken on your system: What happens when you run ansible localhost -m debug -a "msg='{{ [\"fd::\", \"12.34.56.78\"] | ansible.utils.ipwrap }}'"?

[RodCSouza]

[WARNING]: Unable to parse /home/xxxxxxxx/k3s-ansible/hosts.ini as an inventory source
[WARNING]: No inventory was parsed, only implicit localhost is available
localhost | SUCCESS => {
"msg": "{{ ["fd::", "12.34.56.78"] | ansible.utils.ipwrap }}"
}

Looks like the module is not installed, I'm checking.

[RodCSouza]

I would say that the root cause of the issue is related to one of the very first steps of the implementation:
ansible-galaxy install -r ./collections/requirements.yml

This one did nothing in the system, not even if run with sudo, and none of the itens in the collection list had been installed, running the command the system just accepted, without errors or any other information in the command line.

I've installed each of then manually, following the template below, changing the last section with each item of the collection.
ansible-galaxy collection install ansible.utils

[RodCSouza]

Was exactly this, root cause was the installation of "requirements", after installing each package manually, everything run smoothly and I could get K3S HA running successfully.

I would suggest one improvement in the playbook, to include in the tasks, steps to check the availability for each item on the requirements list.