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.

Bug 1790526

Summary: Some PMDAs are missing dependency on PCP package
Product: Red Hat Enterprise Linux 8 Reporter: Jan Kurik <jkurik>
Component: pcpAssignee: pcp-maint <pcp-maint>
Status: CLOSED DUPLICATE QA Contact: Jan Kurik <jkurik>
Severity: low Docs Contact:
Priority: low    
Version: 8.2CC: agerstmayr, jkurik, mgoodwin, nathans, patrickm
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: 8.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: pcp-5.1.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-18 06:24:10 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jan Kurik 2020-01-13 14:38:11 UTC
Description of problem:
Installation of some PMDAs on a fresh RHEL-8.2 system fails due to missing dependency on pcp package.

This is the list of failing PMDAs:

pcp-pmda-dm pcp-pmda-bash pcp-pmda-cifs pcp-pmda-gfs2 pcp-pmda-gpfs pcp-pmda-gpsd pcp-pmda-news pcp-pmda-pdns pcp-pmda-snmp pcp-pmda-bind2 pcp-pmda-cisco pcp-pmda-ds389 pcp-pmda-mailq pcp-pmda-mysql pcp-pmda-nginx pcp-pmda-redis pcp-pmda-samba pcp-pmda-smart pcp-pmda-trace pcp-pmda-apache pcp-pmda-dbping pcp-pmda-mounts pcp-pmda-oracle pcp-pmda-shping pcp-pmda-zimbra pcp-pmda-bonding pcp-pmda-postfix pcp-pmda-rsyslog pcp-pmda-systemd pcp-pmda-activemq pcp-pmda-ds389log pcp-pmda-memcache pcp-pmda-netfilter pcp-pmda-nvidia-gpu

Version-Release number of selected component (if applicable):
* pcp-5.0.2-2.el8

How reproducible:
Always

Steps to Reproduce:
1. On a fresh RHEL-8.2 system without installed pcp package install any of PMDAs reported above
# yum install -y pcp-pmda-activemq

2. Run an installation script of the PMDA
# cd /var/lib/pcp/pmdas/activemq/ && ./Install

Actual results:
The installation fails with a message similar to this one (different PMDAs reports different line numbers):

./Install: line 16: /etc/pcp.env: No such file or directory

Expected results:
The installation is passing without errors.

Additional info:
* A similar error is generated during uninstallation of such PMDA.
* This issue occures randomly during automated testing of PMDAs, when an affected PMDA is installed before explicit installation of pcp package.

Comment 1 Nathan Scott 2020-03-18 06:24:10 UTC
Minor packaging issue, will be resolved via rebase.

*** This bug has been marked as a duplicate of bug 1792971 ***