Red Hat Bugzilla – Bug 488548
Reactivation key from one org is migrated to the another org with system migration.
Last modified: 2009-09-10 15:48:37 EDT
Description of problem: Reactivation key from one org is migrated to the another org with system migration. Version-Release number of selected component (if applicable): Satellite-5.3.0-RHEL5-re20090227.1-i386-embedded-oracle.iso How reproducible: Steps to Reproduce: 1. create 2 orgs org1 & org2 with trust. 2. register a system to org1. 3. login to org1 4. give the system management and provisioning entitlement 5. navigate to the SDC of the system and Details->Reactivation 6. generate a new key 7. from the command line of the satellite server migrate the system to org2 8. migrate-system-profile --username=USERNAME --password=PASSWORD --systemId=SYSTEMID --to-org-id=TO_ORG_ID 9. login to org2 10. give the migrated system from step 8 management and provisioning entitlement. 11. navigate to the SDC of the system and Details->Reactivation Actual results: Notice that the reactivation key you generated from org1 is available. If you try to register that system with the reactivation key now, the system will be registered to org1 Expected results: Additional info:
Since this one should be in the API logic, I'll investigate.
git commit: 1d670116eb2e60dae08bd02d70916260ec4e0534 While working on the solution for this one, I actually found a couple of similar issues that needed to be addressed. As a result, this solution addressed the following issues: 1. The issue as reported... During a system migration, remove the reactivation key associated with the system. 2. During a system migration, remove any custom values that have been defined for the system. (e.g. Values found under Systems->System->Details->Custom Info) 3. During a system migration, migrate any configuration files associated with the system to the new org. This includes config files found in System->Configuration->View/Modify->Locally-Managed and Local Sandbox.
mass move to ON_QA
verified Satellite-5.3.0-RHEL5-re20090401.0-i386-embedded-oracle.iso tested all the 3 scenarios from comment#3
re-verified staged sat530 w/ build 7/24 all 3 scenarios from comment#3 worked as indicated. moving to RELEASE_PENDING
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html