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

Bug 2021010

Summary: Can't show PromQL for the button is disabled when click inspect on 2 dashboards on Developer console
Product: OpenShift Container Platform Reporter: hongyan li <hongyli>
Component: MonitoringAssignee: Andrew Pickering <anpicker>
Status: CLOSED DUPLICATE QA Contact: hongyan li <hongyli>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.10CC: amuller, anpicker, aos-bugs, erooth, jfajersk, juzhao
Target Milestone: ---   
Target Release: ---   
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: 2021-11-09 07:00:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
yaml file for example app none

Description hongyan li 2021-11-08 05:15:41 UTC
Created attachment 1840643 [details]
yaml file for example app

Description of problem:
Can't show PromQL for the button is disabled when click inspect on the following 2 dashboards on Developer console
Kubernetes / Compute Resources / Namespace (Workloads)
Kubernetes / Compute Resources / Workload

Version-Release number of selected component (if applicable):
4.10.0-0.nightly-2021-11-04-001635

How reproducible:
always

Steps to Reproduce:
1. Create prometheus-example-app with attached yaml file under default namespace
2. Enable user-workload monitoring
3. Got to Developer console-->Observe
4. Enable show default namespace
5. Click tab Dashboard and select one of the above dashboards, click inspect
6. Found can't click 'Show PromQL' to see the PromQL 

Actual results:


Expected results:


Additional info:

Comment 4 Andrew Pickering 2021-11-09 07:00:59 UTC
Closing as this appears to be a duplicate of bug 2020498

*** This bug has been marked as a duplicate of bug 2020498 ***