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).
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.
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.
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.
This was delivered with Satellite 6.0 which was released on 10 September 2014.