System information

You can use the hammer acti vati o n-key l i st --o rg ani zati o n-i d ORG-ID command to
verify that the activation keys have been recreated. Ensure you use the correct organization ID.
You can also log in to the WebUI as an administrator to verify that the activation keys were created.
Ensure you are in the correct organization, and then navigate to Con t en t → Act ivation Keys.
The following example illustrates the use of the command-line tools to verify the import of activation
keys.
Examp le 3.12. Verif ying t h e Imp o rt o f Activat ion Keys
# hammer activation-key list --organization-id 3
ID | NAME | CONSUMED | LIFECYCLE ENVIRONMENT | CONTENT VIEW
2 | 1-rhel6-puppet | 0 of Unlimited | | ak_2
1 | 1-rhel5-puppet | 0 of Unlimited | | ak_1
Report a bug
3.7.7. T ransit ioning Kickst art Profiles
The Satellite transition tools do not migrate entire kickstart profiles. Due to some significant
differences between the Satellite 5 and Satellite 6 infrastructures, there is no suitable migration path
between the two versions.
The transition tools can migrate kickstart scripts, and these can be used in Satellite 6 Provisioning
Templates, which are an approximation of kickstart profiles.
Exp o rting Kickst art Script s
The transition tools extract and export kickstart scripts from kickstart profiles as part of the overall
export process on the Satellite 5 server. These scripts are stored in the ki ckstart-scri pts. csv
file in the export archive, which is copied to the Satellite 6 server.
Imp o rtin g T emp lat e Sn ip p ets
When you extract the export archive onto the Satellite 6 server, the hammer i mpo rt command uses
the ki ckstart-scri pts. csv file to create template snippets. These snippets are in the form of
%pre and %post scripts that you can use with any new kickstart profiles in Satellite 6.
Report a bug
3.7.8. T ransit ioning Configurat ion Channels t o Puppet Modules
Red Hat Satellite 5 uses configuration channels to support configuration file management.
Configuration channels are collections of configuration entries, which in turn specify files and values
that Satellite 5 applies to systems that are registered to it. Configuration channels support the upload
of flat files for delivery to associated systems.
Satellite 6 uses Puppet to provide improved configuration management; consequently, part of the
transition process requires that configuration channels be converted into a single Puppet module.
The export process on Satellite 5 includes the latest revision of all configuration files. The import
process uses this information to perform the following tasks:
Red Hat Sat ellit e 6 .0 T ransit ion G uid e
36