Bug 2050005 - Plugin module IDs can clash with console module IDs causing runtime errors
Summary: Plugin module IDs can clash with console module IDs causing runtime errors
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.11.0
Assignee: Vojtech Szocs
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-03 02:28 UTC by Alexey Kazakov
Modified: 2022-08-10 10:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 10:46:42 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Spinner (53.72 KB, image/png)
2022-02-03 02:28 UTC, Alexey Kazakov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 11062 0 None open Bug 2050005: Fix webpack module federation runtime chunk ID clashes 2022-02-15 20:12:08 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:47:06 UTC

Description Alexey Kazakov 2022-02-03 02:28:24 UTC
Created attachment 1858792 [details]
Spinner

Description of problem:

We have four OSD 4.9.15 clusters. Web console in three of them doesn't show any nodes in Compute->Nodes. Just endless spinner.

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

4.9.15

How reproducible:

Open Web Console. Go to Compute->Nodes

Actual results:

There is an endless spinner.

Expected results:

The list of the nodes.

Additional info:

Different people tried it in different browsers (FF, Chrome). Hard refresh and incognito/private mode do not help.

There is an error in the JS console:
```
Component does not exist in module main-chunk-1f54cb223a8d2a70b2c4.min.js:1
    loadComponent main-chunk-1f54cb223a8d2a70b2c4.min.js:1
    (Async: promise callback)
    loadComponent main-chunk-1f54cb223a8d2a70b2c4.min.js:1
    componentDidUpdate main-chunk-1f54cb223a8d2a70b2c4.min.js:1
    us vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    xc vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    unstable_runWithPriority vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:187283
    zi vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    xc vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    lc vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    Ui vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    unstable_runWithPriority vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:187283
    zi vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    Ui vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    Hi vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    Pe vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
    Kt vendors~main-chunk-06305bb3ecd0f117e7d6.min.js:186970
```

We do not see this error in the only cluster which shows the nodes.

Comment 1 Robb Hamilton 2022-02-03 15:08:40 UTC
@Alexey, can you create a HAR file while reproducing the bug in order to help with troubleshooting?  See https://support.zendesk.com/hc/en-us/articles/4408828867098-Generating-a-HAR-file-for-troubleshooting

Comment 3 Alexey Kazakov 2022-02-03 17:19:57 UTC
Sure. I've attached a HAR file.

Comment 8 Yadan Pei 2022-03-07 02:43:35 UTC
1. clone latest console code

2. cd frontend; yarn install
 
3. cd dynamic-demo-plugin; yarn install; yarn build, check generated dist (production build)
search 'webpackChunk' in 'plugin-entry.js', webpackChunk string appear as webpackChunkconsole_demo_plugin instead of just webpackChunk
search 'webpackChunk' in 'exposed-listPage-chunk-9145a0ed989f51a8e54b.min.js', webpackChunk string appear as webpackChunkconsole_demo_plugin instead of just webpackChunk

4. cd dynamic-demo-plugin; yarn install; yarn build-dev, check generated dist (devel build)
search 'webpackChunk' in 'plugin-entry.js', webpackChunk string appear as webpackChunkconsole_demo_plugin instead of just webpackChunk
search 'webpackChunk' in 'exposed-exampleProxyPage-chunk.js', webpackChunk string appear as webpackChunkconsole_demo_plugin instead of just webpackChunk

Moving to VERIFIED

Comment 10 errata-xmlrpc 2022-08-10 10:46:42 UTC
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


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