Loading...

XML

Word

Printable

Type: Bug
Resolution: Done-Errata
Priority: Normal
Fix Version/s: rhos-18.0 FR 2 (Mar 2025)
Affects Version/s: rhos-18.0 FR 1 (Nov 2024)
Component/s: openstack-ceilometer
Labels:
None

Story Points:
0
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Docs Approval:
?
Fixed in Build:
telemetry-operator-container-1.0.7-3
Regression:
None
Intelligence Requested:
Market:
Errata Link:
https://errata.engineering.redhat.com/advisory/146727

Sprint:
CloudOps 2024 Sprint 24, CloudOps 2024 Sprint 25, CloudOps 2024 Sprint 26, CloudOps 2024 Sprint 27, CloudOps 2025 Sprint 1
sprint_count:
5
Severity:
Moderate

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Follow the discussion between Takashi and myself in this patch:

https://review.opendev.org/c/openstack/ceilometer/+/933309/comment/004a3295_bc001fed/

It seems that I was wrong, and if Prometheus retrieves metrics still exposed from a Compute node where the VM is not longer there, it would be exposing the same metric one and again.

Reproduce and see if the behaviour requires unregistering

links to

RHBA-2025:146727 Release of containers for RHOSO OpenStack Podified operator

mentioned in: Page Loading...

Assignee:: Juan Larriba

Reporter:: Juan Larriba

QA Contact:: Leonid Natapov

Team:: rhos-dfg-cloudops

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2024/11/25 2:27 PM

Updated:: 2025/03/20 8:17 AM

Resolved:: 2025/03/20 8:17 AM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

PagerDuty