In my playbook firewall.yaml I first create a http-alt service, and then enable it in a subsequent task (I think this is the approach that must be taken? I tried to do it all in one but the role didn't seem to like that, and it seemed sensible to me.)
What happened:
In my playbook
firewall.yaml
I first create ahttp-alt
service, and then enable it in a subsequent task (I think this is the approach that must be taken? I tried to do it all in one but the role didn't seem to like that, and it seemed sensible to me.)ansible-playbook firewall.yaml -v --check
The subsequent task fails because it does not recognise the service created in the previous task.
What you expected to happen:
The task to pass in check mode. I'd be fine even if it had something like the official Ansible documentation suggests:
ignore_errors: "{{ ansible_check_mode }}"
How to reproduce it (as minimally and precisely as possible):
With the following variables in your playbook using this role:
Anything else we need to know?:
Environment:
0.9.3
nftables
core 2.15.0
1.4.4