Bug 1901447

Summary:	Page gets blanks when YAML editor is cleared in policy creation page
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Karel Srot <ksrot>
Component:	GRC & Policy	Assignee:	Yu Cao <ycao56>
Status:	CLOSED ERRATA	QA Contact:	Derek Ho <dho>
Severity:	medium	Docs Contact:	Mikela Dockery <mdockery>
Priority:	unspecified
Version:	rhacm-2.1	CC:	gghezzo
Target Milestone:	---	Flags:	gghezzo: rhacm-2.1.z+ gghezzo: rhacm-2.2+
Target Release:	rhacm-2.1.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhacm-2.1.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-02-17 18:19:07 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 Karel Srot 2020-11-25 09:19:07 UTC

Description of problem:

Web page content gets blank when the YAML editor content is deleted.
See steps to reproduce below.

Not sure if this is specific to Policy creation page. I just tried Cluster creation page and that works OK.

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


How reproducible:
Alwyas

Steps to Reproduce:
1. visit multicloud/policies/create
2. click to YAML editor
3. press Ctrl+A, then Ctrl-C, then Ctrl-X  to copy and remove the content
4. press Ctrl-V to paste the content back

At this moment a different bug can be seen. Notice that the 'namespace' line is underlined because there is no namespace and namespace is mandatory field.
This is perfectly find, it is just strange that this error is not indicated in the YAML editor since the very beginning.

5. press Ctrl-A and Ctrl-X again to remove the content
6. observe that the page got blank

Actual results:
pages gets blank

Expected results:
page should not get blank, there should be just no content in the YAML editor

Additional info:
Proposing High severity. Although the bug is not blocking, it has definitely impact on user experience.

Comment 1 Ginny Ghezzo 2020-11-25 20:41:00 UTC

Thanks Karel! The team will take a look at this asap. I agree that this is a high impact and would like to change the severity to medium: "Major impact to a feature but does not prevent its execution" . If you disagree, please change it back.

Comment 2 Karel Srot 2020-11-25 21:37:08 UTC

I am OK with the updated severity. Thank you.

Comment 10 errata-xmlrpc 2021-02-17 18:19:07 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 (Moderate: Red Hat Advanced Cluster Management 2.1.3 security and bug fix 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-2021:0607