Fix --tags=start regression

Related to #425 (Github Pull Request)
This commit is contained in:
Slavi Pantaleev 2020-03-29 15:48:46 +03:00
parent a8f4b2a755
commit c655a6467a

View File

@ -28,11 +28,11 @@
delegate_to: 127.0.0.1 delegate_to: 127.0.0.1
become: false become: false
- name: Populate service facts - block:
- name: Populate service facts
service_facts: service_facts:
when: ansible_distribution != 'Archlinux'
- name: Fail if service isn't detected to be running - name: Fail if service isn't detected to be running
fail: fail:
msg: >- msg: >-
{{ item }} was not detected to be running. {{ item }} was not detected to be running.
@ -41,29 +41,24 @@
with_items: "{{ matrix_systemd_services_list }}" with_items: "{{ matrix_systemd_services_list }}"
when: when:
- "ansible_facts.services[item + '.service']|default(none) is none or ansible_facts.services[item + '.service'].state != 'running'" - "ansible_facts.services[item + '.service']|default(none) is none or ansible_facts.services[item + '.service'].state != 'running'"
- ansible_distribution != 'Archlinux' when: " ansible_distribution != 'Archlinux'"
# Currently there is a bug in ansible that renders is incompatible with systemd. - block:
# service_facts is not collecting the data successfully. # Currently there is a bug in ansible that renders is incompatible with systemd.
# Therefore iterating here manually # service_facts is not collecting the data successfully.
- name: Fetch systemd information # Therefore iterating here manually
- name: Fetch systemd information
systemd: systemd:
name: "{{ item }}" name: "{{ item }}"
register: systemdstatus register: systemdstatus
with_items: "{{ matrix_systemd_services_list }}" with_items: "{{ matrix_systemd_services_list }}"
when:
- ansible_distribution == 'Archlinux'
- name: Fail if service isn't detected to be running - name: Fail if service isn't detected to be running
fail: fail:
msg: >- msg: >-
{{ item.item }} was not detected to be running. {{ item.item }} was not detected to be running.
It's possible that there's a configuration problem or another service on your server interferes with it (uses the same ports, etc.). It's possible that there's a configuration problem or another service on your server interferes with it (uses the same ports, etc.).
Try running `systemctl status {{ item.item }}` and `journalctl -fu {{ item.item }}` on the server to investigate. Try running `systemctl status {{ item.item }}` and `journalctl -fu {{ item.item }}` on the server to investigate.
with_items: "{{ systemdstatus.results }}" with_items: "{{ systemdstatus.results }}"
loop_control: when: "item.status['ActiveState'] != 'active'"
label: "{{ item.name }}" when: "ansible_distribution == 'Archlinux'"
when:
#- "ansible_facts.services[item + '.service']|default(none) is none or ansible_facts.services[item + '.service'].state != 'running'"
- "item.status['ActiveState'] != 'active'"
- "ansible_distribution == 'Archlinux'"