Bug 1878375

Summary: Topology issue when creating 2 instances of the same operator backed service
Product: OpenShift Container Platform Reporter: Jeff Phillips <jephilli>
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED ERRATA QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: high    
Version: 4.6CC: aos-bugs, nmukherj, spathak
Target Milestone: ---   
Target Release: 4.6.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Version: 4.6.0-0.nightly-2020-09-10-145837 Cluster ID: e3a0cb08-86db-4b5a-872d-27118405f8cc Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.102 Safari/537.36
Last Closed: 2020-10-27 16:40:12 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:
Attachments:
Description Flags
No topology issue when creating 2 instances of the same operator backed service none

Description Jeff Phillips 2020-09-12 15:21:13 UTC 
Description of problem:

In a project, if I do Add > Operator Backed > Percona Mongo DB, in topology I get an operator backed grouping (PSM badge) with a single SS.

When I repeat the process, rather than getting another operator backed grouping, it adds a second SS to the same grouping AND it renames the Operator Backed Grouping (PSM) 

This process should yield in 2 separate operator backed groupings in topology, each with their own contents.

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


How reproducible:


Steps to Reproduce:
1. Install an operator
2. In dev perspective, use the Add -> Operator Backed tile to add the operator to the project.
3. Go back and add the same operator again but with a different name.

Actual results:

Topology view shows both operator instances as a single instance with the workloads from each instance included.

Expected results:

Topology shows two operator groupings with the appropriate names and workloads.

Additional info:
Comment 2 spathak@redhat.com 2020-09-18 22:44:46 UTC 
Created attachment 1715439 [details]
No topology issue when creating 2 instances of the same operator backed service
Comment 3 spathak@redhat.com 2020-09-18 22:46:27 UTC 
Verified on build version: 4.6.0-0.nightly-2020-09-18-071428
Browser version: Chrome 84
Comment 6 errata-xmlrpc 2020-10-27 16:40:12 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 (OpenShift Container Platform 4.6 GA Images), 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:4196