Bug 1801983

Summary: Monitoring Dashboards: k8s-resources-workloads-namespace don't always set a Type by default
Product: OpenShift Container Platform Reporter: Yadan Pei <yapei>
Component: Management ConsoleAssignee: Andrew Pickering <anpicker>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.4CC: aos-bugs, jokerman, yapei
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:36:06 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:

Description Yadan Pei 2020-02-12 03:27:48 UTC
Description of problem:
Type should have default Type selected when Namespace is changed

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. cluster admin view 'k8s-resources-workloads-namespace' dashboard at Monitoring -> Dashboard page
2. Change Namespace to other namespaces like 'openshift-authentication'

Actual results:
2. Only 1 type in Type dropdown, but it's not selected by default, this is different from the behavior in Grafana

Expected results:
2. A type should be always selected by default

Additional info:

Comment 4 Yadan Pei 2020-02-20 05:50:59 UTC
Steps to verify:
1. cluster admin view 'k8s-resources-workloads-namespace' dashboard at Monitoring -> Dashboard page
2. Change Namespace to other namespaces like 'openshift-authentication', Type dropdown is set as 'deployment' by default, when change namespaces in variable dropdown, Type is automatically changed based on resource type in that namespace
3. Change dashboard to 'k8s-resources-workload', when value of Namespace dropdown is changed, Workload & Type are changed accordingly

The reported issue has been fixed, verified on     4.4.0-0.nightly-2020-02-19-041512

Comment 6 errata-xmlrpc 2020-05-04 11:36: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.