Bug 1146838
| Summary: | pcp timezone oddity | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marko Myllynen <myllynen> |
| Component: | pcp | Assignee: | Nathan Scott <nathans> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | brolley, fche, mgoodwin, nathans, pcp, scox |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-19 12:09:54 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: | |||
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Ok, so the format is popular in some circles, the timezone name followed by the UTC offset where times ahead of UTC a prefixed with -.
For most people something like AWST-8 is a complete mystery ("Is that American West Summer or Standard Time, are they 8 hours behind UTC?"), it would be much better for PCP to report times in UTC+N format which most people would be able to decipher.
Thanks.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. This was addressed in upstream PCP 3.12.2 by switching to more common ISO 8601 type offsets in pmrep & friends. |
Description of problem: On a system which has timezone set to EEST (=UTC+3) pcp(1) reports: # pcp -a 20140925.15.33 Performance Co-Pilot configuration on server.example.com: archive: 20140925.15.33 platform: Linux server.example.com 3.16.2-201.fc20.x86_64 #1 SMP Mon Sep 15 19:57:50 UTC 2014 x86_64 hardware: 2 cpus, 1 disk, 1 node, 2002MB RAM timezone: EEST-3 services: pmcd pmcd: Version 3.9.5-1, 8 agents pmda: pmcd proc xfs linux mmv jbd2 ds389 ds389log pmlogger: primary logger: server.example.com/20140925.15.33 So while EEST is correct the "-3" part is confusing. Considering that in many countries the concept of using abbreviations like PDT or ACST is alien, ideally the timezone could be printed like "EEST (UTC+3)". Thanks.