unknown url type: "" when running init@homeserver.yml playing role tasks in init-server/install-pkgs.yml #9

New Issue

admin · 2026-05-28T11:18:49Z

admin commented

2026-05-28 11:18:49 +00:00

This is the full error return:

Note that more precisely, this was the result when running:

ansible-playbook --ask-pass --ask-become-pass -i hosts.yml init@homeserver.yml --check

The versions of the files mentioned that were used during execution have not yet been pulled/pushed into this bare repo, yet.

This is the full error return: <img width="840" alt="image.png" src="attachments/9cf14a97-3100-4b10-94bb-d8a2347adf0b"> Note that more precisely, this was the result when running: ```bash ansible-playbook --ask-pass --ask-become-pass -i hosts.yml init@homeserver.yml --check ``` The versions of the files mentioned that were used during execution have not yet been pulled/pushed into this bare repo, yet.

image.png

17 KiB

admin added the fix/semantic_error label 2026-05-28 11:18:49 +00:00

admin self-assigned this 2026-05-28 11:18:49 +00:00

admin added this to the SUKAATO debugging project 2026-05-28 11:18:49 +00:00

admin added this to the debug bootstrapping of armitage milestone 2026-05-28 11:28:20 +00:00

admin commented

2026-05-29 01:12:40 +00:00

It seems that the error was due to the task files of the init-server role--as used in the init@homeserver.yml play--having a semantically incorrect conditional case that their execution was contingent on.

Specifically, setting task when attribute to something like ${x} is defined or ${x} is undefined doesn't actually work despite what Ansible's Jinja2 documentation else. Surprisingly, using ${x} is not None or ${x} is None also leads to errors.

Turns out the solution is to instead use constructs like: ${x} != None or ${x} == None.

It seems that the error was due to the task files of the `init-server` role--as used in the `init@homeserver.yml` play--having a semantically incorrect conditional case that their execution was contingent on. Specifically, setting task `when` attribute to something like `${x} is defined` or `${x} is undefined` doesn't actually work despite what Ansible's Jinja2 documentation else. Surprisingly, using `${x} is not None` or `${x} is None` also leads to errors. Turns out the solution is to instead use constructs like: `${x} != None` or `${x} == None`.

admin closed this issue

2026-05-29 01:12:40 +00:00

admin modified the project from SUKAATO debugging to skato-ansible debugging

2026-05-29 18:10:35 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: admin/skato-ansible#9

unknown url type: "" when running init@homeserver.yml playing role tasks in init-server/install-pkgs.yml #9

`unknown url type: ""` when running `init@homeserver.yml` playing role tasks in `init-server/install-pkgs.yml` #9