Hide Forgot
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