-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-9.6
-
None
-
pcp-6.3.7-5.el9
-
No
-
Moderate
-
6
-
rhel-pt-pcp
-
ssg_platform_tools
-
21
-
2
-
QE ack, Dev ack
-
False
-
False
-
-
No
-
PT PCP 2025 S04, PT PCP 2025 S05, PT PCP 2025 S06, PT PCP 2025 S07, PT PCP 2025 S08, PT PCP 2025 S09
-
Pass
-
Automated
-
Unspecified Release Note Type - Unknown
-
-
All
-
None
John Harrigan recently reported the following issue to me:
On my laptop I've been adding and removing files in the openmetrics/config.d directory. As expected I'm seeing the metrics dynamically being added/removed as I work in that directory. These three metrics did have scripts associated with them but have since been removed. $ pminfo openmetrics.rfchassis openmetrics.RFtest openmetrics.RFpdus Error: openmetrics.rfchassis: Unknown metric name Error: openmetrics.RFtest: Unknown metric name Error: openmetrics.RFpdus: Unknown metric name At this time the dir contains these files: $ ls /var/lib/pcp/pmdas/openmetrics/config.d/ grafana.url kepler.url RFchassis.sh RFpdu1.sh RFpdu2.sh RFvars.cfg However, the corresponding 'openmetrics.control' metrics persist for those three metrics. $ pmrep openmetrics.control.fetch_time o.c.fetch_time o.c.fetch_time o.c.fetch_time o.c.fetch_time o.c.fetch_time o.c.fetch_time o.c.fetch_time o.c.fetch_time o.c.fetch_time control grafana kepler RFchassis rfchassis RFtest RFpdus RFpdu1 RFpdu2 The three metric columns in BOLD (rfchassis, RFtest and RFpdus) no longer exist in the openmetrics/config.d directory but their 'control' are still displayed. Even after a system reboot, the same behavior persists.
This is a failure to correctly deal with metric sources that have been removed.
There is a TODO comment in rescan_confdir() within pmdaopenmetrics python code that describes what needs to be done - "nuke sources related to removed files".
- causes
-
-
- Release Pending
-
- is blocked by
-
-
- Closed
-
- links to
-
RHBA-2025:147780
pcp bug fix and enhancement update
