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 1773459

Summary: pcp-pmda-postfix has no dependency on perl-Time-HiRes
Product: Red Hat Enterprise Linux 8 Reporter: Christian Horn <chorn>
Component: pcpAssignee: Nathan Scott <nathans>
Status: CLOSED ERRATA QA Contact: Jan Kurik <jkurik>
Severity: low Docs Contact:
Priority: unspecified    
Version: 8.1CC: agerstmayr, jkurik, mgoodwin, mnewsome, nathans, patrickm
Target Milestone: rcKeywords: Bugfix, Triaged
Target Release: 8.2Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: pcp-5.0.2 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-04-28 15:40:22 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Christian Horn 2019-11-18 08:06:02 UTC
Description of problem:
pcp-pmda-postfix has no dependency on perl-Time-HiRes

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

How reproducible:
always

Steps to Reproduce:
1. install minimal rhel8.1
2. dnf -y install pcp-zeroconf pcp-pmda-postfix
3. cd /var/lib/pcp/pmdas/postfix
4. ./Install

Actual results:

[root@rhel8u1a postfix]# ./Install 
Can't locate Time/HiRes.pm in @INC (you may need to install the Time::HiRes module) (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at /var/lib/pcp/pmdas/postfix/pmdapostfix.pl line 19.
BEGIN failed--compilation aborted at /var/lib/pcp/pmdas/postfix/pmdapostfix.pl line 19.
Can't locate Time/HiRes.pm in @INC (you may need to install the Time::HiRes module) (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5) at /var/lib/pcp/pmdas/postfix/pmdapostfix.pl line 19.
BEGIN failed--compilation aborted at /var/lib/pcp/pmdas/postfix/pmdapostfix.pl line 19.
Install: cannot determine the Performance Metrics Domain from domain.h.perl
[root@rhel8u1a postfix]# 

Expected results:
Should we pull in perl-Time-HiRes via dependencies?

Comment 1 Nathan Scott 2019-11-19 23:14:14 UTC
| Should we pull in perl-Time-HiRes via dependencies?

Yep.

Comment 3 Jan Kurik 2020-01-17 05:53:56 UTC
Works as expected on the latest 5.0.2-2 build of PCP.

Comment 5 errata-xmlrpc 2020-04-28 15:40:22 UTC
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, 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-2020:1628