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:
If a pcp utility (i.e. atop or pmrep) uses a folio file to work with an archive set, the utility is not able to find archives in case the folio files contains links to archives outside of "/tmp" directory.
Version-Release number of selected component (if applicable):
pcp-5.1.0-2.el8
How reproducible:
Always
Steps to Reproduce:
1. Make sure you have at least one archive file in /var/log/pcp/pmlogger/$(hostname)
2. Create a folio file from archives in /var/log/pcp/pmlogger/$(hostname)
# /usr/libexec/pcp/bin/mkaf /var/log/pcp/pmlogger/$(hostname) > \
/tmp/pcp.archives.folio
3. Use the folio file i.e. with atop
# pcp atop -r /tmp/pcp.archives.folio
Actual results:
pcp-atop: Cannot open archive "/tmp//var/log/pcp/pmlogger/ci-vm-10-0-137-213.hosted.upshift.rdu2.redhat.com/20200525.04.16
Expected results:
pcp-atop works with all the archive files listed in the folio
Additional info:
As can be seen in the example output of atop command, atop is prefixing every archive filename in the folio with "/tmp/" prefix. This invalidates the file name and the archive can not be found then.
The same happen for i.e. pmrep command:
# pmrep -D pmapi --archive-folio /tmp/pcp.archives.folio :sar
pmNewContext(2, "/tmp//var/log/pcp/pmlogger/ci-vm-10-0-137-213.hosted.upshift.rdu2.redhat.com/20200525.04.16") <::> returns No such file or directory
pmrep: No such file or directory
The problem occurs due to the 'dir' prefix (of the path to the folio) being prepended to each archive path in the folio, which fails when those paths are absolute paths rather than relative. The folio may contain absolute paths if the original mkaf specifies absolute paths, as was done in the reproducer steps in Comment#0.
Resolved with the following upstream commit and QA updates for pcp-5.2.1:
commit 70c77e6107aaf654e3cbaefc41e655e68583b934 (upstream-goodwinos/master)
Author: Mark Goodwin <mgoodwin>
Date: Wed Sep 23 11:44:37 2020 +1000
libpcp: handle absolute paths to archives when using --archive-folio
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 (pcp 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-2021:1754