Bug 1347095
Summary: | 6.2 Beta2 - Sync Status page not drawn properly if sync in progress | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Geoff Gatward <ggatward> | ||||
Component: | WebUI | Assignee: | Walden Raines <walden> | ||||
Status: | CLOSED ERRATA | QA Contact: | Roman Plevka <rplevka> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.2.0 | CC: | bbuckingham, bkearney, egolov, mmccune, rplevka, sthirugn, tcarlin | ||||
Target Milestone: | Unspecified | Keywords: | Regression, Triaged | ||||
Target Release: | Unused | ||||||
Hardware: | x86_64 | ||||||
OS: | Linux | ||||||
URL: | http://projects.theforeman.org/issues/15499 | ||||||
Whiteboard: | |||||||
Fixed In Version: | rubygem-katello-3.0.0.53-1 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2016-07-27 11:43:41 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: | |||||||
Attachments: |
|
Description
Geoff Gatward
2016-06-16 04:01:25 UTC
We should re-test this once the fix for this bz lands: https://bugzilla.redhat.com/show_bug.cgi?id=1315610 if that fixes this bug, we can close this one out as a dupe. (In reply to Mike McCune from comment #1) > We should re-test this once the fix for this bz lands: > > https://bugzilla.redhat.com/show_bug.cgi?id=1315610 > > if that fixes this bug, we can close this one out as a dupe. This is most likely a dupe because I realized that the progress bar was missing while I was fixing this because of missing assets. The fix for bug #1315610 should also fix this. I am moving this to to ON_QA. Please test once SNAP 17.0 is released. It will contain https://bugzilla.redhat.com/show_bug.cgi?id=1315610 FAILED QA: sat6.2.0 beta (GA17.0) There are no CSS errors, however the issue described still persists. (see attached screenshot). The webbrowser console shows a javascript error ("TypeError: t.attr is not a function") Created attachment 1170747 [details]
sync_status - error
(In reply to Roman Plevka from comment #6) > FAILED QA: > sat6.2.0 beta (GA17.0) > > There are no CSS errors, however the issue described still persists. > (see attached screenshot). > > The webbrowser console shows a javascript error ("TypeError: t.attr is not a > function") Note that this only happens in Firefox and is unrelated to the initial cause of this bug. (In reply to Walden Raines from comment #8) > Note that this only happens in Firefox and is unrelated to the initial cause of this bug. Not true. Getting this error also in Chrome Version 51.0.2704.84 (64-bit) However, the error is gone as soon as the Sync is complete and the page renders correctly again (In reply to Roman Plevka from comment #9) > (In reply to Walden Raines from comment #8) > > > Note that this only happens in Firefox and is unrelated to the initial cause of this bug. > > Not true. Getting this error also in > Chrome Version 51.0.2704.84 (64-bit) > > However, the error is gone as soon as the Sync is complete and the page > renders correctly again After further discussion on IRC it became clear that this error only happens when you reload the page while a sync is running. Created redmine issue http://projects.theforeman.org/issues/15499 from this bug Upstream bug component is WebUI Revision 43ddadae Added by Walden Raines about 6 hours ago Fixes #15499: fix JS error on sync management page. There was a JS error on the sync management page that was causing the page to break. This fixes the JS error by putting the HREF on the element as was originally intended. http://projects.theforeman.org/issues/15499 Revision eb6fda2b Added by Walden Raines about 2 hours ago Merge pull request #6143 from waldenraines/15499 Fixes #15499: fix JS error on sync management page. VERIFIED on sat6.2.0 snap18.1 -the page now renders correctly with no errors in the console. 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-2016:1501 |