RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

# ansible --version
ansible [core 2.13.3]

# cat junk.yml 
---
- hosts: all
  become: true
  tasks:
    - name: get service facts
      service_facts:

# cat inventory 
localhost  ansible_connection=local

# ansible-playbook -i inventory junk.yml 

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
ok: [localhost]

TASK [get service facts] *******************************************************
[WARNING]: Unable to query 'service' tool (1):
ok: [localhost]

PLAY RECAP *********************************************************************
localhost                  : ok=2    changed=0    unreachable=0    failed=0    skipped=0    rescued=0    ignored=0   


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Could you share more information on the node running the service_facts task ? (os release, python version, etc...)

It would be great to get the playbook execution with more verbosity.

The warning is coming from [1] only if the service command doesn't return anything. At least RHEL 8/9 (and maybe 7 too) nodes shouldn't rely on the service command but systemd instead.

This change seems to be introduced in 2.13 via [2].

The interesting part in the output is the service tool name : "1"

Instead of "1" we should have the full path to "service" binary [3].

[1] https://github.com/ansible/ansible/blob/v2.13.3/lib/ansible/modules/service_facts.py#L108-L110
[2] https://github.com/ansible/ansible/commit/699ecb83082b3b24a1a0a21cfadf19eda8891bff
[3] https://github.com/ansible/ansible/blob/v2.13.3/lib/ansible/modules/service_facts.py#L221

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (ansible-core bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2182