Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Instance Name: Not Defined
Build: CSProcessor Builder Version 1.7
Build Filter: null
Build Name: 11169, System Engine User Guide-1.1-1
Build Date: 12-11-2012 14:09:19
Created attachment 663289[details]
screenshot
Description of problem:
On page 26 of the System Engine User Guide, the screenshot is outdated.
New screenshot enclosed.
Then once you've created the Subscription Management Application you need to:
- Click Attach a subscription
- Select the subscription you want to attach from the list of available ones
- Confirm attachement
- Download manifest
The manifest import in System Engine can also take quite a bit of time (minutes) and it's confusing, the user can read progress in /var/log/pulp/pulp.log
(In reply to comment #9)
> The manifest import in System Engine can also take quite a bit of time
> (minutes) and it's confusing, the user can read progress in
> /var/log/pulp/pulp.log
Have been importing the manifest file for over 10 minutes now..
(In reply to comment #10)
> (In reply to comment #9)
> > The manifest import in System Engine can also take quite a bit of time
> > (minutes) and it's confusing, the user can read progress in
> > /var/log/pulp/pulp.log
>
> Have been importing the manifest file for over 10 minutes now..
Total import time: 26mins!
We definitely better document this and warn people.
Created attachment 663289 [details] screenshot Description of problem: On page 26 of the System Engine User Guide, the screenshot is outdated. New screenshot enclosed.