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 1125008 - Transition guide details - what will / won't be transitioned
Summary: Transition guide details - what will / won't be transitioned
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs Transition Guide
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: David O'Brien
QA Contact: Athene Chan
URL:
Whiteboard:
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2014-07-30 20:09 UTC by Andrew Schofield
Modified: 2019-09-25 20:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 12:20:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Andrew Schofield 2014-07-30 20:09:46 UTC
Description of problem:

(Caveat - I've not tried to transition)

Detail what will and will not be transitioned (we know content won't be - how can we ensure content is the same - we (currently) use customized channels not sync'd to RHN). What about activation keys, kickstart configuration, groups, orgs etc.

What actions will need to be taken to get the transitioned data in a state where it can be used again.

How do you migrate clients from Satellite 5 to Satellite 6 (and utilise the transitioned data - are client changes required etc?)

We also run PE (Puppet Enterprise) - how do we transition this to Satellite 6 (and migrate clients etc).

Comment 1 RHEL Program Management 2014-07-30 20:14:06 UTC
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.

Comment 3 Athene Chan 2014-08-14 21:22:19 UTC
Hello Andrew,

My apologies for the late reply. This bug slipped through. 

We are creating a transition guide for the GA Release that should answer some of these questions.  To ensure that your questions can be addressed, I am assigning this bug to our Transition Guide writer, David O'Brien.

Thank you once again for your feedback.

Cheers,
Athene

Comment 6 David O'Brien 2014-08-25 07:24:58 UTC
Most of the information available about what can be transitioned, and how to do it, is in the upcoming Transition Guide, schedule for release with Sat6 GA.

This guide also contains an FAQ that describes what you can and can't expect from the transition tools at this stage.

Comment 8 Bryan Kearney 2014-09-11 12:20:17 UTC
This was delivered with Satellite 6.0 which was released on 10 September 2014.


Note You need to log in before you can comment on or make changes to this bug.