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

Ansible complain with error about handler: "no service or tool found for: named" #6

Closed
marcinpraczko opened this issue Mar 20, 2017 · 2 comments
Assignees

Comments

@marcinpraczko
Copy link
Owner

Ansible complain with following error:

RUNNING HANDLER [ansible-role-named : Stop named - RedHat] *********************
fatal: [midnightconman-fixes.named]: FAILED! => {"changed": false, "failed": true, "msg": "no service or tool found for: named"}
@marcinpraczko marcinpraczko self-assigned this Mar 20, 2017
@marcinpraczko
Copy link
Owner Author

During testing under docker there is a possible issue with starting named via systemctl (RedHat 7)

This is demonstrated with this error:

[root@466c4b42a37d /]# systemctl status named.service
Failed to get D-Bus connection: Operation not permitted

@marcinpraczko
Copy link
Owner Author

marcinpraczko commented Mar 20, 2017

Even when running molecule docker driver with privileged module, this - didn't help:

# molecule.yml
docker:
  privileged: True  # This was added
  containers:

marcinpraczko added a commit that referenced this issue Mar 20, 2017
As docker driver have some issues to run services which not allow test this role
as expected. This commit adds vagrant driver and forces using it.

This slows down testing (docker can be build faster), however allow fully testing
configuration like on real system (services, permissions, etc)

Related with issues:
- #6
- GHMP-6
marcinpraczko added a commit that referenced this issue Mar 20, 2017
This is fix for RHEL tasks which are using proper handler now for restarting named.
This commit fixed issue with handler however permissions must be adjusted (rasied issue: #7)

Related with issues:
- #6
- GHMP-6
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

1 participant