Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2057881

Summary:	MetalLB: speaker metrics is not updated when deleting a service
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Networking	Assignee:	Sabina Aledort <saledort>
Networking sub component:	Metal LB	QA Contact:	Arti Sood <asood>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	medium
Version:	4.11
Target Milestone:	---
Target Release:	4.10.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-04-21 13:15:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2056967
Bug Blocks:

Description OpenShift BugZilla Robot 2022-02-24 07:13:26 UTC

+++ This bug was initially created as a clone of Bug #2056967 +++

Description of problem:
MetalLB speaker metrics is not updated when deleting a service.


Version-Release number of selected component (if applicable):
v4.10.0.202202160023.p0.g6c9b074.assembly.stream

How reproducible:
Always.

Steps to Reproduce:
1. Install MetalLB through metallb-operator.
2. Create a LoadBalancer service.
3. Check the advertising speaker metrics.
4. Delete the service.
5. Check the advertising speaker metrics.

Actual results:
The metric of a delete service is part of the advertising speaker metrics after deleting it.

Expected results:
The metric of a delete service should be deleted from the advertising speaker metrics after deleting it.

Comment 7 errata-xmlrpc 2022-04-21 13:15:55 UTC

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 (Moderate: OpenShift Container Platform 4.10.10 bug fix and security update), 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://access.redhat.com/errata/RHSA-2022:1356