Created attachment 1576533 [details] After upgrade UI get distorted. Description of problem: Satellite UI get distorted after customer DB upgrade from 6.5 to 6.6. Version-Release number of selected component (if applicable): 6.5 to 6.6 How reproducible: 1/1 Steps to Reproduce: 1. Customer DB upgrade from 6.5 to 6.6.0 Snap5 completed successfully. 2. Version upgraded successfully, hammer ping working fine. # rpm -q satellite satellite-6.6.0-5.beta.el7sat.noarch # hammer ping candlepin: Status: ok Server Response: Duration: 306ms candlepin_auth: Status: ok Server Response: Duration: 22ms pulp: Status: ok Server Response: Duration: 749ms pulp_auth: Status: ok Server Response: Duration: 465ms foreman_tasks: Status: ok Server Response: Duration: 4ms Actual results: After Upgrade Satellite UI get broken. Expected results: Satellite UI should open successfully Additional info:
I think I've found the reason for this behavior: while doing backups, we're saving the whole `/var/lib/foreman` directory, that also includes `/var/lib/foreman/public/assets`, and during cloning, we're restoring the assets, that might eventually conflict with the current installation (the reason why it seemed to work sometimes even with this file is probably just the naming - it probably affects the system only when the name of asset file from backup appears earlier in the listing than the file from packaging. I'm filing a separate BZ for backup/restore to handle the assets in backups. However, since the satellite-clone has it's own code for restoring, it needs to be fixed there as well, and that's probably the fix we need to get this BZ resolved. @john: mind having a look?
> However, since the satellite-clone has it's own code for restoring, it needs > to be fixed there as well, and that's probably the fix we need to get this > BZ resolved. > > @john: mind having a look? Yes, I can take a look at this. I filed https://github.com/RedHatSatellite/satellite-clone/issues/360 > A BZ for making satellite-clone to use the foreman-maintain restore procedures https://bugzilla.redhat.com/show_bug.cgi?id=1720141 Thanks, we actually just had a discussion about this and plan to change this in sat-clone
Can we test out https://github.com/RedHatSatellite/satellite-clone/pull/361?
Moving to POST as the upstream PR has been merged.
(In reply to John Mitsch from comment #19) > Can we test out https://github.com/RedHatSatellite/satellite-clone/pull/361? I tested the same with the upstream master branch(https://github.com/RedHatSatellite/satellite-clone.git) and didn't face any UI related issue. GUI was working as expected.
I checked the same with the latest snap and didn't observe this issue(Satellite UI get distorted after customer DB upgrade from 6.5 to 6.6). I will mark this bug verified once Bugzilla: #1727320 get a fix.
Checked (based on previous comments) that the satellite-clone 1.4.1 does not extract the asset files from the backup archive used for clone.
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/RHSA-2019:3172