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:
Having a playbook with "metrics_query_service: yes" or "metrics_graph_service: yes" installs and configures pcp/pmproxy, but does not start the pmproxy service.

Version-Release number of selected component (if applicable):
* RHEL-8.3.0-20200701.2
* pcp-5.1.1-3.el8
* rhel-system-roles-1.0-16.el8

How reproducible:
* always

Steps to Reproduce:
1. Install rhel-system-roles-1.0-16.el8 and ansible
2. Run a playbook using "linux-system-roles.metrics" role having set variable "metrics_query_service: yes" and/or "metrics_graph_service: yes". An example of such a playbook is attached to this bug (see "tests_fullstack.yml").

Actual results:
pmproxy service is installed and configured, but not started

Expected results:
The "linux-system-roles.metrics" with set variables "metrics_query_service: yes" or "metrics_graph_service: yes" should install configure and start the following services:
* pmcd
* pmlogger
* pmie
* pmproxy
* redis
* grafana-server

Additional info:
The issue IMO is in pmproxy.yml tasks file, which is missing explicit start of the pmproxy service. I am attaching fixed pmproxy.yml file to this bug.

Created attachment 1711182 [details]
tests_fullstack.yml

Created attachment 1711183 [details]
pmproxy.yml

Hi Nathan, can you please confirm the problem and whether you can provide a fix?

Yep, good catch Jan!

And I believe fix is correct too except for a minor cut+paste problem where it mentions pmie in the description instead of pmproxy.
I'll update that and get this merged in the upstream repositories today.

This is the following commit in linux-system-roles/metrics:

commit ed19969e9045916518e6d4eb3f363eb3e2e01c2f
Author: Jan Kurik <jkurik>
Date:   Tue Aug 18 14:03:26 2020 +1000

    Ensure pmproxy service is enabled and started when requested
    
    Resolves Red Hat BZ #1868378

Verified on rhel-system-roles-1.0-19.el8 build.

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