Description of problem: migrate-rhs-classic-to-rhsm --rhn-to-rhsm is broken ------------ # migrate-rhs-classic-to-rhsm --rhn-to-rhsm Starting migration to RHSM... Red Hat username: qa Red Hat password: Traceback (most recent call last): File "/usr/bin/migrate-rhs-classic-to-rhsm", line 500, in <module> main() File "/usr/bin/migrate-rhs-classic-to-rhsm", line 496, in main rhn_to_rhsm() File "/usr/bin/migrate-rhs-classic-to-rhsm", line 161, in rhn_to_rhsm rhn_migrate_classic_to_rhsm() File "/usr/bin/migrate-rhs-classic-to-rhsm", line 125, in rhn_migrate_classic_to_rhsm migrate.MigrationEngine().main(args=["--force"]) File "/usr/share/rhsm/subscription_manager/migrate/migrate.py", line 760, in main self.cp = self.get_candlepin_basic_auth_connection(self.secreds.username, self.secreds.password) File "/usr/share/rhsm/subscription_manager/migrate/migrate.py", line 275, in get_candlepin_basic_auth_connection self.cp_provider = inj.require(inj.CP_PROVIDER) File "/usr/share/rhsm/subscription_manager/injection.py", line 102, in require return FEATURES.require(feature, *args, **kwargs) File "/usr/share/rhsm/subscription_manager/injection.py", line 72, in require raise KeyError("Unknown feature: %r" % feature) KeyError: "Unknown feature: 'CP_PROVIDER'" ------------ Version-Release number of selected component (if applicable): # rpm -qa |grep subscription-manager* subscription-manager-migration-1.12.14-7.el6.x86_64 subscription-manager-1.12.14-7.el6.x86_64 subscription-manager-migration-data-2.0.13-1.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Perform the upgrade steps using the "migrate-rhs-classic-to-rhsm" script as mentioned in https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Storage/3/html-single/Console_Installation_Guide/index.html#sect-Upgrading_Red_Hat_Storage_Console 2. migrate-rhs-classic-to-rhsm --rhn-to-rhsm fails with the above mentioned error 3. Actual results: Script fails to migrate from rhn to rhsm Expected results: migrate script should NOT fail Additional info: More details about this bug will be posted soon
Based on my testing, looks like this is happening during the Upgrade testing from errata.stage due to the updates on the following dependent packages which is currently available in Stage: ---- subscription-manager-migration-1.12.14-7.el6.x86_64 subscription-manager-1.12.14-7.el6.x86_64 subscription-manager-migration-data-2.0.13-1.el6.noarch ---- The same script works fine with the following versions, if installed from RHN Live. ------ subscription-manager-migration-data-2.0.5-1.el6.noarch subscription-manager-1.9.11-1.el6.x86_64 subscription-manager-migration-1.9.11-1.el6.x86_64 ------ So, if that is true, this issue will be seen by the customers once the related Errata having the updates for "subscription-manager-migration-*" is out, which would prevent them from using the migrate script.
This is seen during Upgrading Red Hat Storage Console 2.1 Update 4 to Red Hat Storage Console 3.0 using the "migrate-rhs-classic-to-rhsm" script
Reproduction report =================== Successfully reproduced the issue. The script fails before it is able to do any changes to the system. System is still registered to RHN and configured for RHS Console 2.1. -> System is in original state. Workaround ========== Temporary downgrade subscription-manager: # yum downgrade subscription-manager-1.9.11-1.el6 subscription-manager-migration-1.9.11-1.el6 Then continue according to documentation. Note: 'yum update' in Step 9 of "Procedure 3.7. Upgrading Red Hat Storage Console 2.1 Update 4 to Red Hat Storage Console 3.0 using Subscription Manager" will make sure you have back the latest subscription-manager (after your successfull migration).
Verified in rhsc-branding-rhs-2.1.6-1.0.el6rhs
Edited the doc text. Please review and sign-off.
(In reply to Shalaka from comment #15) > Edited the doc text. Please review and sign-off. Thanks. Looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2014-1723.html