Bug 1965519

Summary: Editing CRs is sometimes extremely frustrating because of status updates
Product: OpenShift Container Platform Reporter: Erik M Jacobs <ejacobs>
Component: Management ConsoleAssignee: Jakub Hadvig <jhadvig>
Status: CLOSED NOTABUG QA Contact: Yadan Pei <yapei>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.7CC: aos-bugs, jokerman
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-06-01 07:52:30 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 Erik M Jacobs 2021-05-27 20:47:16 UTC 
As an example, the cluster logging operator frequently updates the status of the ClusterLogging CRs. Every time this happens, the web console reports that the item has changed and suggests a reload.

If you are trying to make an edit to a CR where this is the case, the experience is maddening. You have to make your change fast enough that it happens before the CR updates under the covers.

kubectl/oc's edit behavior doesn't have this problem, as some reconciliation of the changes are done on the back end. However, the web interface will NOT let you save your changes because the displayed YAML no longer matches.
Comment 1 Jakub Hadvig 2021-06-01 07:52:30 UTC 
Closing this BZ since transition this to a story. It’s not a small change.

Jira story - https://issues.redhat.com/browse/CONSOLE-2889