Bug 912375

commit 767f9a8ad6041ab6b0f251f61bb6927f1f96df89
Author: Alex Wood <awood>
Date:   Thu Sep 19 15:13:33 2013 -0400

    Refactor credentials gathering.
    
    Additionally, use a more generic term that "System Engine".

Verifying the following continuous integration build on a RHEL6 system since rhnreg_ks now blocks registration of a RHEL7 system...

[root@jsefler-6 ~]# rpm -q subscription-manager-migration
subscription-manager-migration-1.10.5-1.git.0.86042ca.el6.x86_64



[root@jsefler-6 ~]# rhn-migrate-classic-to-rhsm --help
Usage: rhn-migrate-classic-to-rhsm [OPTIONS]

Options:
  -h, --help            show this help message and exit
  -f, --force           ignore channels not available on RHSM
  -g, --gui             launch the GUI tool to attach subscriptions, instead
                        of auto-attaching
  -n, --no-auto         don't execute the auto-attach option while registering
                        with subscription manager
  -s SERVICELEVEL, --servicelevel=SERVICELEVEL
                        service level to follow when attaching subscriptions,
                        for no service level use --servicelevel=""
  --serverurl=SERVERURL
                        specify the subscription management server to migrate
                        to
  --redhat-user=REDHATUSER
                        specify the Red Hat user name
  --redhat-password=REDHATPASSWORD
                        specify the Red Hat password
  --subscription-service-user=SUBSERVICEUSER
                        specify the subscription service user name
  --subscription-service-password=SUBSERVICEPASSWORD
                        specify the subscription service password
  --no-proxy            don't use RHN proxy settings with subscription
                        management server
  --org=ORG             organization to register to
  --environment=ENVIRONMENT
                        environment to register to


^^^ VERIFIED: Notice the new command line options to specify --redhat-user=REDHATUSER --redhat-password=REDHATPASSWORD --subscription-service-user=SUBSERVICEUSER --subscription-service-password --org=ORG --environment=ENVIRONMENT which can all be used to satisfy the request in comment 0.



[root@jsefler-6 ~]# rhn-migrate-classic-to-rhsm 
Red Hat username: qa
Red Hat password: 
Subscription Service username: non-existant-user
Subscription Service password: 
Unable to connect to certificate server: Invalid Credentials.  See /var/log/rhsm/rhsm.log for more details.
[root@jsefler-6 ~]# 

^^^ VERIFIED: The labels for interactive credential prompts have changed as expected.  The "System Engine" label has been replaced with a generic "Subscription Service" label.



[root@jsefler-6 ~]# rhn-migrate-classic-to-rhsm --redhat-user=qa --redhat-password=redhatqa --subscription-service-user=stage_test_12 --subscription-service-password=redhat --org=7065298 --no-auto --serverurl=subscription.rhn.stage.redhat.com:443/subscription

Retrieving existing RHN Classic subscription information...

+-----------------------------------------------------+
System is currently subscribed to these RHN Classic Channels:
+-----------------------------------------------------+
rhel-x86_64-server-6

+-----------------------------------------------------+
Installing product certificates for these RHN Classic channels:
+-----------------------------------------------------+
rhel-x86_64-server-6

Product certificates installed successfully to /etc/pki/product.

Preparing to unregister system from RHN Classic...
System successfully unregistered from RHN Classic.

Attempting to register system to Red Hat Subscription Management...
The system has been registered with ID: 69bbfe34-c837-43e9-b560-ab016291a201 
System 'jsefler-6.usersys.redhat.com' successfully registered to Red Hat Subscription Management.

[root@jsefler-6 ~]# 

^^^ VERIFIED: the migration script can be run with options to avoid interactive prompting.  (Note: I did not specify --environment because the hosted stage subscription management server does not support environments, but a katello server does and should only be required when more than one environment is available to the Subscription Service credentials.

Verifying Version...
[root@jsefler-7 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 0.9.2-1
subscription-manager: 1.10.11-1.el7
python-rhsm: 1.10.11-1.el7


[root@jsefler-7 ~]# rhn-migrate-classic-to-rhsm --help
Usage: rhn-migrate-classic-to-rhsm [OPTIONS]

Options:
  -h, --help            show this help message and exit
  -f, --force           ignore channels not available on RHSM
  -g, --gui             launch the GUI tool to attach subscriptions, instead
                        of auto-attaching
  -n, --no-auto         don't execute the auto-attach option while registering
                        with subscription manager
  -s SERVICELEVEL, --servicelevel=SERVICELEVEL
                        service level to follow when attaching subscriptions,
                        for no service level use --servicelevel=""
  --serverurl=SERVERURL
                        specify the subscription management server to migrate
                        to
  --redhat-user=REDHATUSER
                        specify the Red Hat user name
  --redhat-password=REDHATPASSWORD
                        specify the Red Hat password
  --subscription-service-user=SUBSERVICEUSER
                        specify the subscription service user name
  --subscription-service-password=SUBSERVICEPASSWORD
                        specify the subscription service password
  --no-proxy            don't use RHN proxy settings with subscription
                        management server
  --org=ORG             organization to register to
  --environment=ENVIRONMENT
                        environment to register to


VERIFIED: rhn-migrate-classic-to-rhsm now supports new CLI options --redhat-user=REDHATUSER --redhat-password=REDHATPASSWORD --subscription-service-user=SUBSERVICEUSER --subscription-service-password=SUBSERVICEPASSWORD --org=ORG --environment=ENVIRONMENT which can all be used to satisfy the request in comment 0.


Comment 3 demonstrates the usage of these new CLI options.

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.