Bug 1811739

Summary: kube-proxy metrics are missing
Product: OpenShift Container Platform Reporter: Juan Luis de Sousa-Valadas <jdesousa>
Component: NetworkingAssignee: Juan Luis de Sousa-Valadas <jdesousa>
Networking sub component: openshift-sdn QA Contact: Anurag saxena <anusaxen>
Status: CLOSED ERRATA Docs Contact:
Severity: unspecified    
Priority: unspecified CC: anbhat, anusaxen
Version: 4.4Flags: anusaxen: needinfo-
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Cause: Changes on kube-proxy metrics implementation made some metrics disappear during the kubernetes 1.17 rebase. Consequence: Changes on kube-proxy metrics implementation made some metrics disappear during the kubernetes 1.17 rebase. Fix: Change how we publish metrics in SDN. Result: Metrics are back
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:19:06 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:    
Bug Blocks: 1810725    

Description Juan Luis de Sousa-Valadas 2020-03-09 16:25:49 UTC
This bug was initially created as a copy of Bug #1810725

I am copying this bug because: 



Description of problem:Apparently all kubeproxy metrics are missing in 4.4 while they are present in 4.3 which were added via SDN-405 


Version-Release number of selected component (if applicable):4.4.0-0.nightly-2020-03-04-103509


How reproducible:Always


Steps to Reproduce:
1.Login to prometheus and observe kubeproxy metrics
2.
3.

Actual results: Kubeproxy metrics missing


Expected results:Kubeproxy metrics are expected


Additional info:

Comment 4 Anurag saxena 2020-03-12 14:59:49 UTC
@Aniket, Sure i am looking at this

Comment 5 Anurag saxena 2020-03-12 16:07:43 UTC
Looks good to me on 4.5.0-0.nightly-2020-03-11-161108
All kubeproxy metrics are being reported fine now.

Comment 7 errata-xmlrpc 2020-07-13 17:19:06 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, 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/RHBA-2020:2409