Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When running a playbook with rhel-system-roles.metrics role on RHEL-7 or RHEL-6, ansible reports missing redis service
Version-Release number of selected component (if applicable):
* RHEL_7_8 or RHEL_6_10
* ansible-2.8 or ansible-2.9
* rhel-system-roles-1.0-16
How reproducible:
* Always
Steps to Reproduce:
1. On a system running the minimal rhel-7.8 or rhel-6.10 image install ansible 2.8 or ansible-2.9
2. Create a playbook using linux-system-roles.metrics role
3. Run the playbook
Actual results:
TASK [linux-system-roles.metrics : Ensure scalable query service is running and enabled on boot] ***
task path: /tmp/tmp.Q46FZPCbOz/roles/rhel-system-roles.metrics/tasks/redis.yml:4
fatal: [image.qcow2]: FAILED! => {"changed": false, "msg": "Could not find the requested service redis: host"}
Expected results:
The role works on RHEL_7_8 as well as on RHEL_6_10 with ansible-2.8 or ansible-2.9
Additional info:
IMO the issue is caused by missing/disabled repo where redis is located. On RHEL-7 as well as on RHEL-6 the repo is "epel" which is not enabled by default. The repo needs to be explicitly enabled, before usage in the role.
I am not sure that enabling an unsupported repo is desirable in RHEL. We have no precedent for this in other system roles AFAIK, they are meant to configure RHEL, not an unsupported add-on like EPEL.
(In reply to Pavel Cahyna from comment #1)
> I am not sure that enabling an unsupported repo is desirable in RHEL. We
> have no precedent for this in other system roles AFAIK, they are meant to
> configure RHEL, not an unsupported add-on like EPEL.
One possible solution I discussed with Nathan is to support only the basic metric role on all the RHELs, and have the "graph" and "query" scenarios supported on RHEL >= 8 only.
This solution reflects the availability of redis & grafana packages in different versions of RHEL.
(In reply to Jan Kurik from comment #2)
> One possible solution I discussed with Nathan is to support only the basic
> metric role on all the RHELs, and have the "graph" and "query" scenarios
> supported on RHEL >= 8 only.
This solution would not require any code change, only clarification of support status in documentation?
Right, no code changes are required if we document this as requirements constrains.
Will the "Role Variables" section documenting "metrics_graph_service" and "metrics_query_service" variables in https://github.com/linux-system-roles/metrics/blob/master/README.md be the right place ?
(In reply to Jan Kurik from comment #4)
> Right, no code changes are required if we document this as requirements
> constrains.
> Will the "Role Variables" section documenting "metrics_graph_service" and
> "metrics_query_service" variables in
> https://github.com/linux-system-roles/metrics/blob/master/README.md be the
> right place ?
+1 seems like a good place to me.
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 (rhel-system-roles 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/RHEA-2020:4809
Description of problem: When running a playbook with rhel-system-roles.metrics role on RHEL-7 or RHEL-6, ansible reports missing redis service Version-Release number of selected component (if applicable): * RHEL_7_8 or RHEL_6_10 * ansible-2.8 or ansible-2.9 * rhel-system-roles-1.0-16 How reproducible: * Always Steps to Reproduce: 1. On a system running the minimal rhel-7.8 or rhel-6.10 image install ansible 2.8 or ansible-2.9 2. Create a playbook using linux-system-roles.metrics role 3. Run the playbook Actual results: TASK [linux-system-roles.metrics : Ensure scalable query service is running and enabled on boot] *** task path: /tmp/tmp.Q46FZPCbOz/roles/rhel-system-roles.metrics/tasks/redis.yml:4 fatal: [image.qcow2]: FAILED! => {"changed": false, "msg": "Could not find the requested service redis: host"} Expected results: The role works on RHEL_7_8 as well as on RHEL_6_10 with ansible-2.8 or ansible-2.9 Additional info: IMO the issue is caused by missing/disabled repo where redis is located. On RHEL-7 as well as on RHEL-6 the repo is "epel" which is not enabled by default. The repo needs to be explicitly enabled, before usage in the role.