Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
[The following is a summary of discussion between ggainey and awood about the problems surrounding migration of Sat5 clients to a new Sat6 instance]
Description of problem:
Part of moving customer-data from their existing Satellite-5 instance to their shiny-new-Satellite-6 instance involves moving their System profiles to Content Hosts.
We would like to be able to accomplish a workflow something like the following:
* Export Sat5 system-profiles
* Import said profiles and create Sat6 content-hosts
* Generate a CSV file during this process containing the following data:
Sat5SID ; Sat6ConsumerId ; Sat6ActivationKey
* Have rhn-migrate-classic-to-rhsm be able to take advantage of said CSV, in order to attach a client to its related content-host on Sat6
Issues to be resolved around this:
* migrate-classic doesn't understand cloned channels.
channels.software.getDetails(channelLabel) has a field, 'clone_original', which has the label of "the channel this channel was cloned FROM". For the migrate-classic chan-to-PEM mapping to work, the tool would have to be taught to follow that back until clone_orginal is empty (which would be the originating Red Hat channel) and *then* map.
* migrate-classic would need some way to be pointed at the created-CSV mentioned above, and find the entry for its own machine therein
* migrate-classic doesn't currently understand --consumerid or --activationkey
* The created-CSV would need to be placed into some location migrate-classic could pull it from, on the Sat6 system it is going to re-register to.
* Alternately (or perhaps in addition to the above), migrate-classic would need to be able to accept a pointer to said CSV as a local file.
This work would need to be available on RHEL5 and RHEL6 via errata released on or before the GA date of Sat6, in order to facilitate early-adopters' migration process.
This feature request was not implemented and delivered to QE by the rhel-7.1.0 Dev Freeze date of 10/27/2014. Deferring for consideration in next release.
We ended up writing sat5to6 to get the 6.0 transition issue resolved. That is only available to sat5 users, iirc.
I believe Alex has been working on updates to rhn-migrate-to-rhsm that address some of what's in this BZ. Alex?
Yes, bug 1086367, bug 1180273, and bug 1196416 should all handle various migration related enhancements.
Closing this as DUPLICATE of 1196416 even though this bug is actually a duplicate of several different bugs.
*** This bug has been marked as a duplicate of bug 1196416 ***