Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Red Hat Customer
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 1679504
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh109 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
Migrated Products
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
Bug 1679504
-
Grafana: 'USE Method Node' Dashboard shows on the jump list only 3 nodes
Summary:
Grafana: 'USE Method Node' Dashboard shows on the jump list only 3 nodes
Keywords
:
Status
:
CLOSED NOTABUG
Alias:
None
Product:
OpenShift Container Platform
Classification:
Red Hat
Component:
Monitoring
Sub Component:
---
Version:
3.11.0
Hardware:
All
OS:
Linux
Priority:
unspecified
Severity:
medium
Target Milestone:
---
Target Release
:
3.11.z
Assignee:
Sergiusz Urbaniak
QA Contact:
Junqi Zhao
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+
depends on
/
blocked
Reported:
2019-02-21 09:39 UTC by
Gabriel Stein
Modified:
2022-03-13 17:01 UTC (
History
)
CC List:
5 users
(
show
)
fbranczy
gferrazs
minden
mloibl
surbania
Fixed In Version:
Doc Type:
If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
2019-02-25 13:08:55 UTC
Target Upstream Version:
Embargoed:
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Bugzilla
1619132
0
medium
CLOSED
"User not found" error in grafana pod logs, and some metrics could not be viewed from grafana UI
2021-02-22 00:41:40 UTC
Red Hat Bugzilla
1622387
0
unspecified
CLOSED
Multiple Series Error for Disk Space Usage on grafana UI
2021-02-22 00:41:40 UTC
Red Hat Bugzilla
1659441
0
high
CLOSED
Port range from 9000-10000 need to be opened from iptables explicitly after upgrading from 3.10 to 3.11
2023-03-24 14:26:35 UTC
Comment 9
Sergiusz Urbaniak
2019-02-25 13:06:30 UTC
@gabriel does this mean we can close out this issue?
Note
You need to
log in
before you can comment on or make changes to this bug.