Bug 1746706

Summary:	Edit environment will trigger warning alert for reloading current page info
Product:	OpenShift Container Platform	Reporter:	XiaochuanWang <xiaocwan>
Component:	Management Console	Assignee:	Jon Jackson <jonjacks>
Status:	CLOSED ERRATA	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	aos-bugs, jhadvig, jokerman
Target Milestone:	---	Keywords:	Reopened
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:38:14 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 XiaochuanWang 2019-08-29 07:00:31 UTC

Description of problem:
User has a DC and check the DC Environment tab page, the warning alert shows as soon as user input something or click to add a pair of value.

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

How reproducible:
Always

Steps to Reproduce:
1. User has a DC, check the DC environment tab page.
2. Input something for key/value pair
3. (After click Reload button), Click the button "Add Value" or "Add from Config Map or Secret", or "Add All From Config Map or Secret"
4. Wait after all pods are Running.

Actual results:
2 & 3 & 4: Warning alert always shows 
"The information on this page is no longer current.
Click Reload to update and lose edits, or Save Changes to overwrite."

Expected results:
Should not show the alert even when the pods are not ready.

Additional info:

Comment 1 Jakub Hadvig 2019-08-29 09:35:51 UTC

Based on the implementation I see that the notification is on purpose,
so the user will immediately by notified that there is a change and can
handle it.

Based on discussion in: https://github.com/openshift/console/pull/33

Comment 2 Samuel Padgett 2019-08-29 17:02:14 UTC

Are there no env var changes? We should ideally only show the warning if the env vars have changed. Jon was working on a fix.

Comment 4 XiaochuanWang 2019-09-03 01:56:17 UTC

This is not reproduced, verified on 4.2.0-0.nightly-2019-09-02-172410

Comment 5 errata-xmlrpc 2019-10-16 06:38:14 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