Bug 1830046

Summary: Helm rollback or upgrade does not return to previous page
Product: OpenShift Container Platform Reporter: Rohit Rai <rorai>
Component: Dev ConsoleAssignee: Rohit Rai <rorai>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.5CC: aos-bugs, nmukherj
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:33:39 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 Rohit Rai 2020-04-30 19:22:30 UTC 
Description of problem:
When the user completes the helm rollback action they are always brought back to the helm list view. By design the user should be brought back to the page they were viewing where the action was first invoked from.

eg if viewing topology and they invoke the helm rollback action, upon completion the user should be brought back to the topology page.

This is similar to pressing the cancel button.


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


How reproducible: Always


Steps to Reproduce:

1. install a helm chart
2. navigate to the helm chart in the UI (details page or topology)
3. select action rollback
4. on the rollback page select a revision and select rollback


Actual results: user gets redirected to helm list page


Expected results: user is redirected to the page they invoked the rollback action


Additional info:
Comment 3 Gajanan More 2020-05-09 08:32:40 UTC 
I have validated the bugzilla on the
Build: 4.5.0-0.ci-2020-05-09-014245
Browser: Google Chrome Version 81.0.4044.129
Marking this as verfied
Comment 4 errata-xmlrpc 2020-07-13 17:33:39 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-2020:2409