Bug 1848687

Summary: haproxy current sessions data in Prometheus keep increasing
Product: OpenShift Container Platform Reporter: Clayton Coleman <ccoleman>
Component: NetworkingAssignee: Andrew McDermott <amcdermo>
Networking sub component: router QA Contact: Arvind iyengar <aiyengar>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aiyengar, alegrand, amcdermo, anpicker, aos-bugs, bbennett, bperkins, ccoleman, erooth, jlee, kakkoyun, lcosic, mjoseph, mloibl, pkrupa, surbania
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1832539 Environment:
Last Closed: 2020-07-21 10:31: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: 1832539    
Bug Blocks:    
Attachments:
Description Flags
Prometheus graph data from patched cluster version
none
Promethrus Graph data for unpatched cluster environment none

Description Clayton Coleman 2020-06-18 18:18:56 UTC 
+++ This bug was initially created as a clone of Bug #1832539 +++

Description of problem:
From Prometheus, we can see haproxy exporter.

haproxy_frontend_current_session or haproxy_server_current_session should show active sessions but it does not show like that. It seems that the number of sessions keeps increasing. From my test environment, there is no load that's why I can see session decresement after load testing. However, for production cluster, it goes to 15 million with ocp 3.11 and 8k with ocp 4.4
Comment 1 Andrew McDermott 2020-06-19 12:00:52 UTC 
This is POST but adding UpcomingSprint for housekeeping. And:

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.
Comment 4 Arvind iyengar 2020-07-13 08:12:35 UTC 
The PR merge made into "4.4.0-0.nightly-2020-07-08-233114" release. It is noted that the fix works as intended where "haproxy_frontend_current_sessions" shows consistent results during the idle condition in comparison to non patched payload.
Comment 5 Arvind iyengar 2020-07-13 08:13:36 UTC 
Created attachment 1700781 [details]
Prometheus graph data from patched cluster version
Comment 6 Arvind iyengar 2020-07-13 08:14:42 UTC 
Created attachment 1700782 [details]
Promethrus Graph data for unpatched cluster environment
Comment 8 errata-xmlrpc 2020-07-21 10:31: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:2913