Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2090193

Summary: While creating more than one knative service (before the service is up) the nodes overlaps in topology
Product: OpenShift Container Platform Reporter: Sparsh Kesari <skesari>
Component: Dev ConsoleAssignee: Jeff Phillips <jephilli>
Status: CLOSED DUPLICATE QA Contact: spathak <spathak>
Severity: high Docs Contact:
Priority: high    
Version: 4.11CC: cjerolim, divgupta, jephilli, lprabhu, nmukherj
Target Milestone: ---   
Target Release: 4.11.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: 2022-06-16 19:04:00 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
4.11 Overlapped nodes none

Description Sparsh Kesari 2022-05-25 10:47:00 UTC 
Created attachment 1883254 [details]
4.11 Overlapped nodes

Description of problem:
When we add more than one knative service, the added knative node (before the service is up) in the topology view gets overlapped on each other and there is no possible way to move them and separate them.

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

How reproducible:
Always

Steps to Reproduce:
1. Create a new namespace
2. Create a more than one knative service from Import from Git Option
    Git Repo URL : https://github.com/sclorg/nodejs-ex.git
    Resources : Serverless Deployment
3. Visit the topology page before the service is up 
4. The multiple nodes for the service will be overlapped and un separable.

Actual results:
Service Nodes are overlapped and not able to separate them


Expected results:
Separate nodes foe each service 


Additional info:
The nodes get separated once the service is up
Comment 1 Jeff Phillips 2022-06-16 19:04:00 UTC 

*** This bug has been marked as a duplicate of bug 2089675 ***