Bug 2075575 - Local Dev Env - Prometheus 404 Call errors spam the console
Summary: Local Dev Env - Prometheus 404 Call errors spam the console
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.11.0
Assignee: Rastislav Wagner
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-14 15:26 UTC by Andrew Ballantyne
Modified: 2022-08-10 11:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 11:07:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Administrator Dashboard Console Log (8.20 MB, video/quicktime)
2022-04-14 15:26 UTC, Andrew Ballantyne
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11380 0 None open Bug 2075575: Align url polling interval for Overview pages with other pages 2022-04-21 16:24:48 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 11:07:24 UTC

Description Andrew Ballantyne 2022-04-14 15:26:23 UTC
Created attachment 1872550 [details]
Administrator Dashboard Console Log

Description of problem:
When running locally, there seems to be some broken configuration in the prometheus setup. Even more so, the logic causes a very hefty spam of 404 calls.

More so on the Administrator Dashboard page than anywhere else, but it does still periodically trigger on all pages (that I have seen).

This log spam will prevent us from seeing real errors during development.

Version-Release number of selected component (if applicable):
Seems to be a client setup -- 4.11 master code... but I have tested it on these servers:
 - 4.10.0-0.nightly-2022-01-31-012936
 - 4.11.0-0.nightly-2022-04-12-072444

How reproducible:
Local only

Steps to Reproduce:
1. Load up the cluster UI locally
2. Navigate to the Administrator Dashboard
3. See Console Logs

Actual results:
See attached .mov

Expected results:
Not to be spammed -- should error out if the connection isn't valid, and then wait a duration before trying again. Should not spam constant calls

Comment 1 Jakub Hadvig 2022-04-21 12:49:59 UTC
Based on discussion with Rastislav Wagner and Andy Pickering, we are going to fix this bug by bumping the polling interval from 5 to 15 seconds.
Longterm we are going to solve this by introducing a smart polling interval that will increase over time. For that I've created a RFE story to
to keep track https://issues.redhat.com/browse/RFE-2795

Comment 4 Siva Reddy 2022-04-27 22:23:27 UTC
ClusterVersion:
 4.11.0-0.nightly-2022-04-26-030643

Steps to verify:
1. Load up the cluster UI locally
2. Navigate to the Administrator Dashboard
3. See Console Logs  
  
   Now the error logging is more measured and it is not spammed. This is not a permanent fix which will be provided per https://issues.redhat.com/browse/RFE-2795

Comment 8 errata-xmlrpc 2022-08-10 11:07: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 (Important: OpenShift Container Platform 4.11.0 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:5069


Note You need to log in before you can comment on or make changes to this bug.