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.
Bug 887067 - Setting up Manifests
Summary: Setting up Manifests
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs User Guide
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: Athene Chan
QA Contact: Lana Brindley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-14 01:15 UTC by Aurelien Gouny
Modified: 2015-05-11 22:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
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
Last Closed: 2013-10-01 02:59:04 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (110.29 KB, image/png)
2012-12-14 01:15 UTC, Aurelien Gouny 		no flags Details
manage subscriptions (133.14 KB, image/png)
2012-12-14 01:23 UTC, Aurelien Gouny 		no flags Details
register a Subscription Management Application (112.19 KB, image/png)
2012-12-14 01:23 UTC, Aurelien Gouny 		no flags Details
name the Subscription Management Application (93.64 KB, image/png)
2012-12-14 01:25 UTC, Aurelien Gouny 		no flags Details
result page (replaces Figure 5.4) (114.59 KB, image/png)
2012-12-14 01:26 UTC, Aurelien Gouny 		no flags Details
View All

Description Aurelien Gouny 2012-12-14 01:15:06 UTC 
Created attachment 663289 [details]
screenshot

Description of problem:
On page 26 of the System Engine User Guide, the screenshot is outdated.
New screenshot enclosed.
Comment 1 Aurelien Gouny 2012-12-14 01:16:17 UTC 
Also the page name changed from "Summary Overview" to "Overview".
Comment 2 Aurelien Gouny 2012-12-14 01:22:31 UTC 
And the whole subscription thing is outdated as well (Figures 5.3, 5.4).
I've enclosed screenshots of the new process.
Comment 4 Aurelien Gouny 2012-12-14 01:23:01 UTC 
Created attachment 663290 [details]
manage subscriptions
Comment 5 Aurelien Gouny 2012-12-14 01:23:52 UTC 
Created attachment 663291 [details]
register a Subscription Management Application
Comment 6 Aurelien Gouny 2012-12-14 01:25:38 UTC 
Created attachment 663292 [details]
name the Subscription Management Application
Comment 7 Aurelien Gouny 2012-12-14 01:26:23 UTC 
Created attachment 663293 [details]
result page (replaces Figure 5.4)
Comment 8 Aurelien Gouny 2012-12-14 01:30:57 UTC 
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
Comment 9 Aurelien Gouny 2012-12-14 01:42:33 UTC 
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
Comment 10 Aurelien Gouny 2012-12-14 01:50:03 UTC 
(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..
Comment 11 Aurelien Gouny 2012-12-14 02:02:28 UTC 
(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.
Comment 12 Dan Macpherson 2013-02-01 06:52:03 UTC 
Revise Manifest Imports section and screenshots for v.next as per agouny's comments.
Note You need to log in before you can comment on or make changes to this bug.