Bug 2090193 - While creating more than one knative service (before the service is up) the nodes overlaps in topology
Summary: While creating more than one knative service (before the service is up) the n...
Keywords:
Status: CLOSED DUPLICATE of bug 2089675
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Jeff Phillips
QA Contact: spathak@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-05-25 10:47 UTC by Sparsh Kesari
Modified: 2022-06-16 19:04 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-16 19:04:00 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
4.11 Overlapped nodes (915.17 KB, image/png)
2022-05-25 10:47 UTC, Sparsh Kesari
no flags Details

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 ***


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