Bug 1835151
| Summary: | Error navigating to add page immediately after creating Knative Service resource | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Christoph Jerolimov <cjerolim> | ||||
| Component: | Dev Console | Assignee: | Christoph Jerolimov <cjerolim> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Gajanan More <gamore> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.5 | CC: | aos-bugs, jakumar, 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: | Environment: | ||||||
| Last Closed: | 2020-07-13 17:38:25 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: |
|
||||||
I tried to reproduce but wasn't able to reproduce it. I have validated the bugzilla on Build: 4.5.0-0.ci-2020-05-18-204038 Browser: Google Chrome Version 81.0.4044.129 Marking this as verified. 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 This comment was flagged a spam, view the edit history to see the original text if required. |
Created attachment 1687997 [details] Screenshot of the error message Description of problem (by Christian): I encountered this error by navigating to the developer perspective add page immediately after creating the knative service resource from the admin perspective installed operator page. This will probably be hard to reproduce, but we should guard against the following error which resulted in a white screen. Version-Release number of selected component (if applicable): 4.5 How reproducible: Currently not possible for me (Christoph). It should be done by the following steps. Steps to Reproduce: 1. Install serverless operator 2. Create a namespace 3. In Administration perspective create a knative service resource 4. Switch to developer perspective and open "+ Add" Alternative when testing this locally while developing: 1. In frontend/packages/dev-console/src/components/AddPage.tsx change the prop name of one the FirehoseResources. For example change the prop from 'statefulSets' to 'statefulSets_failing'. Actual results: A white screen was shown and this message was logged in the browser console: Uncaught TypeError: Cannot read property 'data' of undefined at EmptyStateLoader (AddPage.tsx:41) at ... Expected results: No error, no white screen. Additional info: