Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Manifest import task progress remains at 0.

Version-Release number of selected component (if applicable):
-Satellite 6.7.0 snap 20

How reproducible:
-Always

Steps to Reproduce:
1. Go to Content > Subscription
2. Upload manifest.
3. Click on task link, given in notification.

Actual results:
- Progress bar is not working and it always remains at 0.

Expected results:
- Progress bar is working and shows right task complete percentage.

Additional info:
- To see task failed or completed, go to Monitor > Task and click on import manifest task.
- Clicking on Dynflow console button gives "Internal Server Error" page. (BZ#1818053)

Created redmine issue https://projects.theforeman.org/issues/29495 from this bug

Note:
The URL in the notification has a trailing forward slash at the end. The JS fetching the details doesn't expect it there and fails to extract the UUID from the url. Consequently it calls to /foreman_tasks/api/tasks//details, which yields a 404

Alternative steps to reproduce:
1) Open details of any task
2) Add a forward slash at the end

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29495 has been resolved.

FailedQA

Tested with:
- Satellite 6.8.0 snap 6

Test steps:
1. Go to Content > Subscription
2. Upload manifest.
3. Click on task link, given in notification.

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 (Important: Satellite 6.8 release), 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-2020:4366