Hide Forgot
Description of problem: regression since 6.3.0 Snap 21 Apparently, the query for the sync status now needs to send a Context parameter. Right now, the server returns a redirect to "select_organization" page in the background, leaving the 'sync pstatus' progress bar without any data: request url: GET https://sat6.com/katello/sync_management/sync_status?repoids[]=7&_=1509966958854 response: 302 Found location: https://sat6.com/select_organization?toState=/katello/sync_management/sync_status This obviously never ends and staying on the page leads to an infinite task polling. How reproducible: Steps to Reproduce: 1. create any repo 2. navigate to sync status 3. expand the created repo and hit sync 4. monitor the progress and outbound traffic Actual results: the sync status GET requests are being redirected to 'select_organization' page, sync status progress bar not updated, page infinitely polling for the sync status. Expected results: sync status retrieved correctly, feeding progress bar with correct data, finishing when sync complete
*** Bug 1513276 has been marked as a duplicate of this bug. ***
*** Bug 1514425 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/21711 from this bug
Upstream bug assigned to walden@redhat.com
PR: https://github.com/Katello/katello/pull/7096
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21711 has been resolved.
Walden, This didn't cherry-pick cleanly, and I'm not that familiar with the codebase. Could you do the pick for me? Thanks, Patrick
*** Bug 1523686 has been marked as a duplicate of this bug. ***
VERIFIED on sat6.3.0-28 there's an organization_id parameter passed to the sync_status request and the request is being replied to by status 200 https://<fqdn>/katello/sync_management/sync_status?repoids[]=1&repoids[]=2&organization_id=1&_=1513241572752 the status bar works and is being updated
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-2018:0336
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-2018:0336