Bug 1745497

Summary:	Can not select metrics if typed partially matched metrics with capital letters
Product:	OpenShift Container Platform	Reporter:	Junqi Zhao <juzhao>
Component:	Management Console	Assignee:	Andrew Pickering <anpicker>
Status:	CLOSED ERRATA	QA Contact:	Viacheslav <mviaches>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.2.0	CC:	aos-bugs, ccoleman, jokerman, spadgett
Target Milestone:	---
Target Release:	4.2.0
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:	2019-10-16 06:37:32 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:

Description Junqi Zhao 2019-08-26 08:56:25 UTC

Description of problem:
Go to query browser, type "ALERT" in the search filed, since we have "ALERTS" in the metrics list, select "ALERTS", but it can not be selected, "ALERTS" won't be added in the search field

same error for capital and low-case letters mixed together, eg: "ALERt"

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-08-25-173945:

How reproducible:
Always

Steps to Reproduce:
1. See the description
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Junqi Zhao 2019-08-26 08:57:49 UTC

no issue if we type lower-cases "alert", "ALERTS" could be selected

Comment 2 Andrew Pickering 2019-08-29 00:44:44 UTC

*** Bug 1746520 has been marked as a duplicate of this bug. ***

Comment 4 Viacheslav 2019-08-29 13:17:38 UTC

Bug still observed on 4.2.0-0.nightly-2019-08-28-235925

Comment 5 Samuel Padgett 2019-08-29 13:21:15 UTC

Your build doesn't have the fix. You need 4.2.0-0.nightly-2019-08-29-041601 or newer

Comment 6 Junqi Zhao 2019-08-30 03:05:04 UTC

issue is fixed with 4.2.0-0.nightly-2019-08-29-170426
autocompletion insert is case insensitive now

Comment 7 errata-xmlrpc 2019-10-16 06:37:32 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-2019:2922