Description of problem:
After upgrading 3.7 or 4.* Satellite to version 5.0.0, the WebUI is broken,
presumably because the CSS have changed significantly but the browser does not
know about it and does not reload them, unless forced.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a 3.7 Satellite, work with it via WebUI.
2. Upgrade it to 5.0.
3. Go to the WebUI.
The layout is broken.
It is possible to fix this by reloading the page (Ctrl + R in my Galeon).
I wonder if:
1) We should use different CSS filenames since the change is so significant. But
it's probably too late into the game for this change.
2) We should put that Ctrl + R step into the upgrade scenario files.
Created attachment 155671 [details]
Example of broken layout
Something like this could be added to rhn-satellite-5-upgrade-scenario-1?.txt:
16. Test/verify new RHN Satellite:
website: check that you can log in, that the basic data is sane, and the
custom RPMs can be downloaded.
+ a refresh (Ctrl + R) of the browser can be needed should the
+ layout of pages be broken.
a thorough evaluation (with some depth) is advised
monitoring: perform steps 13a and 13b (if needed) at this point.
hosted: ensure the satellite is a satellite according to the hosted site
Suggest to change the 'can' with a 'could'
Change committed to SVN, revision 117006.
With rhn-upgrade-5.0.0-4.noarch.rpm on webqa, moving ON_QA.
QA Contact -> ssalevan
Found appropriate text in latest rhn-upgrade RPM; thus this bug is VERIFIED.
Looks good on Stage-verified Satellite; moving to RELEASE_PENDING.
Closed for Satellite 500 Release.