Created attachment 1870672 [details]
404 with ChunkLoadError
Description of problem:
The console plugin for Red Hat Advanced Cluster Management for Kubernetes is sporadically encountering an error. This results in a 404 page being displayed and the plugin being disabled.
Version-Release number of selected component (if applicable): OCP 4.10.3
Steps to Reproduce:
1. Install ACM 2.5 (Seen on various builds from March 28, 2022 to present)
1. Visit All Clusters from cluster switcher
1. Click on various navigation sections, like Cluster, Applications, Governance.
Pages should load without issue.
This may have been caused by a caching directive we had on plugin-entry.js and plugin-manifest.json. We will fix that and monitor if we encounter any further instances of this issue.
Putting on ON_QA since the issue should be fixed by https://github.com/stolostron/console/pull/1486
On ocp 4.11 cluster with payload 4.11.0-0.nightly-2022-04-16-163450, install ACM 2.5 with Snapshot: 2.5.0-SNAPSHOT-2022-04-20-06-50-05.
Visit All Clusters from cluster switcher. Click on various navigation sections, like Cluster, Applications, Governance. It still returns 404 page. Refer to screenshot.
@yanpzhan Had you used this browser with previous versions of the ACM plugin? You may need to clear your browser cache. Also, did the issue persist, or did it resolve after awhile?
In one of your screenshots, I see the message "Code reference resolution failed for plugin". It would be good to see that expanded, and also if it was the same in every case. Also useful to include the network tab to see if there were any failed fetches.
Would I be able to access this environment?
Checked on ocp 4.11 cluster with payload 4.11.0-0.nightly-2022-04-26-181148, install ACM 2.5 with Snapshot 2.5.0-SNAPSHOT-2022-04-29-10-02-38.
Use a new browser which didn't access previous versions of the ACM plugin.
Visit All Clusters from cluster switcher. Click on various navigation sections, like Cluster, Applications, Governance. All could open now.
@yanpzhan Are we OK to close now then?
According to Comment 8, the bug has been fix, move it to Verified.