Bug 1772687
| Summary: | Upgrade from 4.2.2 to 4.2.4 causes Console CSS to break/not render until cache is cleared | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Rob Szumski <rszumski> | ||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.2.z | CC: | aos-bugs, hasha, jokerman, spadgett, yapei | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.3.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Mac OS | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Previously, in some cases after upgrading your cluster, the web console could use cached CSS stylesheets, which would cause some visual issues on load. The problem has been fixed, and the console will correctly use the updated stylesheets after an upgrade.
|
Story Points: | --- | ||||
| Clone Of: | |||||||
| : | 1774508 (view as bug list) | Environment: | |||||
| Last Closed: | 2020-01-23 11:12:49 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1774508, 1780254 | ||||||
| Attachments: |
|
||||||
Hi Sam, The issue described in this bug is CSS loading error after upgrade. What's the root cause of it? It was found in 4.2.2 -> 4.2.4 upgrade but fixed in 4.3, then how can I verify it? I guess if I can verify the fix during a 4.3.x -> 4.3.x upgrade or 4.2.x -> 4.3.x upgrade I would open the networking tab in the browser developer tools prior to loading console. Make sure "Disable Cache" is *not* checked. Load the console after the upgrade. Make sure none of the CSS requests come from cache. You can use the CSS filter for network request. The responses should all have status 200 instead of 304. Check the dev console ignoring the resource cache when loading pages,all network requests status are 200. Verified this bug. 4.2.7->4.3.0-0.nightly-2019-11-19-122017 Safari Version 11.0.3 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:0062 |
Created attachment 1636277 [details] Broken CSS in Console Description of problem: Upgrading from 4.2.2 to 4.2.4 using Safari caused the Console to not render CSS and be completely unusable until the cache was cleared and the browser was restarted. Version-Release number of selected component (if applicable): OCP 4.2.2 How reproducible: Upgrade from 4.2.2 to 4.2.4 using Safari 13.0.3 on MacOS 10.14.6. Steps to Reproduce: 1. Click upgrade in Cluster Settings Actual results: See screenshot