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.

Description of problem:

I believe we need to set expectations with customers and offer a warning (or info) admonition stating that a manifest import can be a lengthy operation.  I believe the length of time needed to complete the import is a function of the amount of channels/repos provided by the manifest.  

Perhaps there is some way to quantify the expected manifest import time for the customer.  This would avoid surprises, and hopefully set expectations properly.

http://documentation-stage.bne.redhat.com/docs/en-US/CloudForms/1.0/html/System_Engine_User_Guide/sect-System_Engine_User_Guide-Content_Providers-Setting_Manifest.html

Change made and committed in revision 0-25

Sarah, you added a note to the right place, but it talks about the wrong issue.

What you wrote about is the delay between giving a machine a subscription, and the time the machine itself sees that it's subscribed.  That belongs in perhaps "5.3. Assign a Subscription".

James was referring to how long it takes to upload a manifest.  The text on "Procedure 3.4. Upload Subscription Manifest" should be something like:

"5. Click the Upload button to upload subscription manifest.  It may take several minutes for the manifest upload to complete".

Rejected based on the doc version in the link in the previous comment.

Document is now available on docs.redhat.com. Please raise a new bug for any further issues.

LKB