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):
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
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.
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.