Bug 1806914

Summary: Dev Catalog should always take us to Topology when in Dev Perspective
Product: OpenShift Container Platform Reporter: Sahil Budhwar <sbudhwar>
Component: Dev ConsoleAssignee: Sahil Budhwar <sbudhwar>
Status: CLOSED ERRATA QA Contact: Gajanan More <gamore>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: aos-bugs, gamore, 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:
: 1810382 (view as bug list) Environment:
Last Closed: 2020-07-13 17:20:54 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:
Bug Depends On:    
Bug Blocks: 1810382    

Description Sahil Budhwar 2020-02-25 10:06:09 UTC 
Description of problem:
When we create some items through the dev-catalog we don't navigate to the topology and this is confusing to the user.

Note: Typically the offenders are Operator Backed instances, which take us to the "Installed Operators resources" page.

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


How reproducible:


Steps to Reproduce:
1. Go to Add flow. Open dev catalog
2. Install operator backed or template
3. Notice, Page redirects to the details page of installed resource

Actual results:
Page redirects to the details page of installed resource

Expected results:
Should redirect to topology page

Additional info:
Comment 3 Gajanan More 2020-03-10 11:15:16 UTC 
I have validated this bug on
Build: 4.5.0-0.ci-2020-03-10-023720
Browser: Google Chrome 78.0.3904.108
Marking this bug as verified.
Comment 5 errata-xmlrpc 2020-07-13 17:20:54 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