Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

systemd service usage failing with Ansible 2.2 #15

Closed
geerlingguy opened this issue Nov 2, 2016 · 3 comments
Closed

systemd service usage failing with Ansible 2.2 #15

geerlingguy opened this issue Nov 2, 2016 · 3 comments

Comments

@geerlingguy
Copy link
Owner

The old init script isn't being picked up until after a system reboot or systemctl daemon-reload on Ubuntu 16.04 (and possibly elsewhere) as of Ansible 2.2.

I get:

TASK [geerlingguy.mailhog : Ensure mailhog is enabled and will start on boot.] *
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "Could not find the requested service \"'mailhog'\": "}

See related: geerlingguy/drupal-vm#958

@travis-south
Copy link

travis-south commented Nov 9, 2016

@geerlingguy, I'm still encountering this issue even on your latest version. I'm using geerlingguy/centos7. For some reason, the ansible_distribution_version|int is interpredted as 0 that's why the Copy mailhog systemd unit file into place (for systemd systems). task is skipped. Same for the firewall role. When I tried removing the int filter, everything worked as expected.

@geerlingguy
Copy link
Owner Author

@travis-south - Right you are—testing a fix now.

@geerlingguy geerlingguy reopened this Nov 9, 2016
@geerlingguy
Copy link
Owner Author

Fixed with above commit. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants