Bug 1801447
| Summary: | Error on the topology page when User tries to connect the node to itself | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Jeff Phillips <jephilli> |
| Component: | Dev Console | Assignee: | Jeff Phillips <jephilli> |
| Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.4 | CC: | aos-bugs, gamore, nmukherj |
| Target Milestone: | --- | ||
| Target Release: | 4.4.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.4.0-0.ci-2020-02-09-194845
Cluster ID: ab36f720-0913-4c27-ad04-8bd7c12537f3
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
|
|
| Last Closed: | 2020-05-04 11:35:28 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: | |||
https://issues.redhat.com/browse/ODC-3014 verified by Aritra Roy 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:0581 |
Description of problem: I was trying to check what happens when we try to connect the node to itself. I am facing this problem. I am unable to open the only topology page of the namespace. When I try to create new deployment, then also it is redirecting to black screen. Version-Release number of selected component (if applicable): How reproducible: consistently Steps to Reproduce: 1. Create new project 2. Create some deployments of knative service type, deployment type 3. Try to connect the knative service node to itself and then try to refresh the page Actual results: you will observe that it will redirect to blank screen. The error from the console: vendors~main-chunk-8a2b868a91615c9e45f4.min.js:161172 Error: No target node found with ID '5a813c31-3cda-4fae-9ae8-71d28ed4d761'. at t.setModel (dev-console-topology-chunk-ea059b00478738a5ce0c.min.js:1) at i (dev-console-topology-chunk-ea059b00478738a5ce0c.min.js:1) at Array.forEach (<anonymous>) at t.fromModel (dev-console-topology-chunk-ea059b00478738a5ce0c.min.js:1) at Ot (vendors~dev-console-topology~git-import-form~pipeline-builder-edit-page~pipeline-builder-page~pipeli~b2c8ca75-chunk-faa21a7b6ae540c8bb4b.min.js:84) at t.r (vendors~dev-console-topology~git-import-form~pipeline-builder-edit-page~pipeline-builder-page~pipeli~b2c8ca75-chunk-faa21a7b6ae540c8bb4b.min.js:84) at dev-console-topology-chunk-ea059b00478738a5ce0c.min.js:1 at Ma (vendors~main-chunk-8a2b868a91615c9e45f4.min.js:161172) at vendors~main-chunk-8a2b868a91615c9e45f4.min.js:161172 at t.unstable_runWithPriority (vendors~main-chunk-8a2b868a91615c9e45f4.min.js:161466) Expected results: Nothing should happen, connecting a node to itself is a no-op. UI refreshes w/o issue. Additional info: