-
Bug
-
Resolution: Done-Errata
-
Normal
-
None
-
pcp-6.2.2-1.el9
-
None
-
None
-
3
-
rhel-pt-pcp
-
ssg_platform_tools
-
20
-
22
-
1
-
QE ack, Dev ack
-
False
-
False
-
-
Yes
-
Red Hat Enterprise Linux
-
PCP Sprint 2, PCP Sprint 3, PCP Sprint 5
-
Unspecified Release Note Type - Unknown
-
None
- There are two ways to install PCP on RHEL systems:
- Use pcp-zeroconf package (recommended way)
- Install the pcp package itself
- If you install pcp-zeroconf it pulls the pcp as a dependency but it is not other way.
- Upon installation of pcp-zeroconf it tunes the pmlogger to collect the samples per 10 seconds in archives.
- But if customer chooses to install the pcp package itself instead of pcp-zeroconf then pmlogger collects samples per 10 minutes in archives.
- While supporting customers we have came across of many cases where customers have preferred to install pcp package instead of pcp-zeroconf and while debugging the 10 minutes of interval made the perf data almost useless.
- So we need to end this discrepancy by:
- keeping only one package to install the pcp stack.
- If both packages are necessary then both the package should follow the same settings especially the 10 seconds of interval.
- If customer choses to install only PCP package then pull the pcp-zeroconf as a dependency.
- split to
-
-
- Closed
-
- links to
-
RHBA-2024:129301
pcp bug fix and enhancement update
