Hide Forgot
Description of problem: In satellite webui the manifest refresh page doesn't update to show that it is complete. If you refresh the manifest then open up the same page in another tab it will be complete and show time stamp. This is leaving people to believe there manifest is not refreshing, when it actually is. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. upload manifest 2. refresh manifest 3. leave same page open Actual results: manifest refresh spins and spins Expected results: manifest refresh to complete and show it completed in real time. Additional info:
Hi Kathryn, I believe this bugzilla raises a couple of issues which we may want to track separately based upon the code that is impacted. 1. Performing a manifest refresh takes a long time. 2. When performing a manifest refresh, if the user opens a new tab (or browser), navigates to Content -> Red Hat Subscriptions -> Manage Manifest, the UI will report that the refresh is complete; however, it is still in progress according to Monitor -> Tasks Do you agree? If so, can we track them with separate bugzillas? Also, which is of most concern to users?
(In reply to Brad Buckingham from comment #7) > Hi Kathryn, > > I believe this bugzilla raises a couple of issues which we may want to track > separately based upon the code that is impacted. > > 1. Performing a manifest refresh takes a long time. > 2. When performing a manifest refresh, if the user opens a new tab (or > browser), navigates to Content -> Red Hat Subscriptions -> Manage Manifest, > the UI will report that the refresh is complete; however, it is still in > progress according to Monitor -> Tasks > > Do you agree? > If so, can we track them with separate bugzillas? Also, which is of most > concern to users? I agree Brad. Think I forgot to split this into two when I noticed the task issue.
Connecting redmine issue http://projects.theforeman.org/issues/20244 from this bug
The current plan from engineering is to address item 2 of comment 7, which stated: 2. When performing a manifest refresh, if the user opens a new tab (or browser), navigates to Content -> Red Hat Subscriptions -> Manage Manifest, the UI will report that the refresh is complete; however, it is still in progress according to Monitor -> Tasks
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/20244 has been resolved.
Created attachment 1314263 [details] New tab shows completed before manifest finishes importing
Created attachment 1314264 [details] Manifest refresh waits until process finishes before updating.
Failed on Satellite-6.3 Snap 11 While the manifest refresh does seem to have been fixed (tested with >2000 subscriptions imported), I hit the issue during initial import (screenshots attached). This is closely related enough to fall under this BZ.
(In reply to Christine Fouant from comment #18) > Failed on Satellite-6.3 Snap 11 > > While the manifest refresh does seem to have been fixed (tested with >2000 > subscriptions imported), I hit the issue during initial import (screenshots > attached). This is closely related enough to fall under this BZ. Does it fail against what is said in comment#13?
(In reply to Walden Raines from comment #19) > (In reply to Christine Fouant from comment #18) > > Failed on Satellite-6.3 Snap 11 > > > > While the manifest refresh does seem to have been fixed (tested with >2000 > > subscriptions imported), I hit the issue during initial import (screenshots > > attached). This is closely related enough to fall under this BZ. > > Does it fail against what is said in comment#13? No, it didn't fail on refreshing. However, QE told me that initial import behavior should also fall under this BZ.
(In reply to Christine Fouant from comment #20) > (In reply to Walden Raines from comment #19) > > (In reply to Christine Fouant from comment #18) > > > Failed on Satellite-6.3 Snap 11 > > > > > > While the manifest refresh does seem to have been fixed (tested with >2000 > > > subscriptions imported), I hit the issue during initial import (screenshots > > > attached). This is closely related enough to fall under this BZ. > > > > Does it fail against what is said in comment#13? > > No, it didn't fail on refreshing. However, QE told me that initial import > behavior should also fall under this BZ. I am going to have to disagree with that given comment#10, comment#11, and comment#13. The time to disapprove of the approach for 6.3 has already passed. I think we should open a new bug for import as they are separate issues anyway.
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
Has this been fixed in the 6.2.x tree as well?