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.

This was a possible guide discussed during an MDP1 docs meeting. Essentially the guide aims to transition users from Satellite 5 to Satellite 6 in that it explains certain Sat 6 features and compares to their equivalents from Sat 5.

Note that the guide will not provide any data migration instructions. It is only for helping current Sat 5 customers with getting used to Sat 6.

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

This BZ is the RFE to create the guide and 1102985 covers what's going to get done for Beta, so it's essentially a duplicate. Anything further for GA+ will be covered by new BZs.

*** This bug has been marked as a duplicate of bug 1102985 ***