Bug 1515527 – Need refresh manually after clear changes when add env from configmap/secret

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1515527 - Need refresh manually after clear changes when add env from configmap/secret

Summary:	Need refresh manually after clear changes when add env from configmap/secret

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Management Console (Show other bugs)
Sub Component:
Version:	3.7.0
Hardware:	Unspecified Unspecified

Priority	low Severity low
Target Milestone:	---
Target Release:	3.9.0
Assigned To:	Samuel Padgett
QA Contact:	Yadan Pei
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-11-20 21:14 EST by Yanping Zhang
Modified:	2018-03-28 10:12 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	Previously, the "Clear Changes" button did not correctly clear edits to the "Environment From" variables in the web console environment variable editor. The button now correctly resets edits to "Environment From" variables.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-03-28 10:12:08 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0489	None	None	None	2018-03-28 10:12 EDT

Groups: None (edit)

Description Yanping Zhang 2017-11-20 21:14:45 EST

Description of problem:
Add env from configmap/secret on dc envirionment page, after choose a configmap/secret, click "Clear Changes", the page doesn't change automatically, need refresh manually. 

Version-Release number of selected component (if applicable):
openshift v3.7.9
kubernetes v1.7.6+a08f5eeb62

How reproducible:
Always

Steps to Reproduce:
1.Create dc and secret.
#oc secrets new testsecret /dev/null
#oc run testdc --image=aosqe/hello-openshift
2.On "hello-openshift" dc page, under "Environment" tab, click "Add ALL Values from Config Map or Secret", choose secret "testsecret", click "Clear Changes".
3.

Actual results:
2.Click "Clear Changes" successfully, but the change is still shown on page, need to refresh the page to make the change disappear.

Expected results:
3.The change should disappear automatically.

Additional info:

Comment 1 Samuel Padgett 2017-11-27 15:14:04 EST

https://github.com/openshift/origin-web-console/pull/2532

Comment 2 openshift-github-bot 2017-11-28 10:45:17 EST

Commits pushed to master at https://github.com/openshift/origin-web-console

https://github.com/openshift/origin-web-console/commit/fa287816e892323c483ad635222740b7e69aa14f
Bug 1515527 - Correctly clear envFrom changes

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1515527

https://github.com/openshift/origin-web-console/commit/3103e3c2d8d250ba728d388f879c6c82b513c592
Merge pull request #2532 from spadgett/clear-env-from

Automatic merge from submit-queue.

Bug 1515527 - Correctly clear envFrom changes

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1515527

/kind bug
/assign @jwforres

Comment 4 Yanping Zhang 2018-01-03 03:25:33 EST

Checked on OCP v3.9.0-0.9.0, when click "Clear Changes" on dc environment tab, the page could get refreshed automatically, and the change disappears.
The bug has been fixed, so move it to Verified.

Comment 7 errata-xmlrpc 2018-03-28 10:12:08 EDT

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-2018:0489

Note You need to log in before you can comment on or make changes to this bug.