Bug 2029797
| Summary: | Uncaught exception: ResizeObserver loop limit exceeded | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Udi Kalifon <ukalifon> | ||||
| Component: | Management Console | Assignee: | Robb Hamilton <rhamilto> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.9 | CC: | aos-bugs, dtaylor, jhadvig, kdoberst, spadgett | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.11.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2022-08-10 10:40:31 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: |
|
||||||
Hi, we recently introduced the ability for our Cypress tests to catch certain exceptions and continue on with tests: https://github.com/openshift/console/pull/10545/files#diff-4387bd8bed040f0832f2d5d6e0042b457bc8909390550bbde652c4659915c40aR15 You can probably update to: Cypress.on('uncaught:exception', (err) => { if (err.message.includes('> Unauthorized') || err.message.includes('ResizeObserver loop limit exceeded')) { console.error('Cypress caught "> Unauthorized exception", continuing tests', err); return false; // test continues } return true; // test fails }); Reassigning to "Special Resource Operator" component team as I don't see this exception installing other operators from OpenShift console UI. This is a legitimate problem, and the runtime error is in the console code. Regardless of what's in the CSV, the console should not have these errors, and we shouldn't be ignoring the exception in our tests. Moving back to the management console component. Dave, do you mind opening a BZ to remove the special case for the unauthorized exceptions as well? Those exceptions should be caught. We should avoid putting in special cases for errors like this and make sure we have a BZ tracking when we do. I am unable to reproduce the bug as written on a fresh 4.9.0-0.nightly-2022-06-08-150705 or 4.11.0-0.nightly-2022-06-06-201913 cluster. It's possible the original bug as written no longer exists? I am, however, able to produce a console error [1] when clicking the `Install` button inside the `Special Resource Operator` modal. I've put up a fix to address this different error in https://github.com/openshift/console/pull/11696. [1] 'resourcePath: no model for "sro.openshift.io~v1beta1~SpecialResource"' Verified on 4.11.0-fc.0 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security update), 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/RHSA-2022:5069 |
Created attachment 1845050 [details] Exception in the Firefox console Description of problem: When going to OperatorHub in the console, and clicking on one of the operators to install it - you get an exception in the browser console. See attached screenshot. This in not noticible to a user, but would fail an automatic test in Cypress because uncaught exceptions in the application under test automatically fail the test. Version-Release number of selected component (if applicable): 4.9.4 How reproducible: 100% Steps to Reproduce: 1. Log in to the UI 2. Make sure you have the browser console open (F12) 3. Navigate to Operators -> OperatorHub 4. Search for "Special Resource Operator" 5. Click on the RedHat-provided operator (not the community one) Actual results: An exception is logged Expected results: No exceptions Additional info: When running with Cypress, you can determine that the exception is: "ResizeObserver loop limit exceeded". This is not visible in the console on a regular browser session, and I'm relying on Cypress for this information.