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.

As previously and repeatedly reported, the libpcp multi-archive code cannot be used properly across routine time zone changes due to libpcp/src/logutil.c line 115/116.  Please remove those checks, which are inconsistent with pmlogextract's handling (a warning message).

Created attachment 1184313 [details]
proposed fix

There appears to be no QA regression fallout, since the error message appears nowhere in multi-archive group tests or outputs.

The proposed fix looks ok. I'm looking into whether the error message should be retired as well.

(In reply to Frank Ch. Eigler from comment #3)
> 
> There appears to be no QA regression fallout, since the error message
> appears nowhere in multi-archive group tests or outputs.

qa test 006 tests for this.

My mistake. It only tests that the error text can be generated.

FWIW, I wouldn't necessarily retire the error code from pmapi.h - just in case some oddball third-party application already mentions it in its source code.

Fixed by upstream commits:

7fcfa821bf9322155d0c3c2538949e588c97f781
e43e3478a2c44c6d48f64c3efb6f0a8257b3c927

Verified for build pcp-3.11.3-3.el7.

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://rhn.redhat.com/errata/RHBA-2016-2344.html