Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-24470

Repository synchronization progress does not get updated in real time on Satellite Web UI's "Content ---> Sync Status" page - RHEL8 Satellite 6.16

XMLWordPrintable

    • Sprint 132, Sprint 133, Sprint 134, Sprint 135, Sprint 136, Sprint 137, Sprint 138, Sprint 139, Sprint 140, Sprint 141
    • Moderate
    • Yes

      Description of problem:
      ----------------------

      While syncing the repository on Red Hat Satellite 6.16 with RHEL-8 as the base OS, the sync progress only shows after refreshing the page, and does not get updated in real-time

      Version-Release number of selected component (if applicable):
      ------------------------------------------------------------

      Red Hat Satellite 6.16 on RHEL-8.9

      How reproducible:
      ----------------

      Always

      Steps to Reproduce:
      ------------------

      1. Enable the repository.

      2. Go to Content ---> Sync Status ---> Check the repository ---> Click on the "Synchronize Now" button

      3. Progress of the sync won't be displayed in real-time. So, refresh the web browser now to see the progress.

      Actual results:
      --------------

      Real-time repository sync progress does not show.

      Expected results:
      ----------------

      Progress of repository sync process should be displayed in real-time.

      Additional info:
      ---------------

      The Content ---> Sync Status page show N/A in all columns of the repository being synced. Screenshots attached to the bugzilla.

      I have tested this on my lab Satellite Server 6.11/6.12/6.13/6.14. The process works there as expected, and shows the progress in real-time.

          There are no Sub-Tasks for this issue.

              jira-bugzilla-migration RH Bugzilla Integration
              rhn-support-ajambhul Anand Jambhulkar
              David Moore David Moore
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: