Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-27938

Registration with GRT fails if RHSM configuration contains old proxy parameters

XMLWordPrintable

    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Rocket
    • Moderate
    • None

      Description of problem:

      If proxy parameters were previously defined in the RHSM configuration, GRT script does not reset the proxy parameters which results in registration failure. 

      How reproducible:

      Always

      Is this issue a regression from an earlier version:

      No

      Steps to Reproduce:

      1. Add proxy variables on RHEL system.
         

         # grep ^proxy /etc/rhsm/rhsm.conf 
   proxy_hostname =proxy.example.com
   proxy_scheme = http
   proxy_port =8080

      2. Register the client using GRT. 

      Actual behavior: 

      • Registration fails with the following messages.

       

        # set -o pipefail && curl -sS --insecure 'https://satellite.example.com/register?activation_keys=GENERAL&force=1&location_id=2&organization_id=1&setup_insights=0&setup_remote_execution=1&setup_remote_execution_pull=0' -H 'Authorization: Bearer TOKEN' | bash
  #
  # Running registration
  #
  This system is currently not registered.
  All local data removed
  subscription-manager is already installed!
  Proxy error: unable to connect to proxy.example.com:8080: Name or service not known (error code -2)

      Expected behavior:

      The global registration script should reset the proxy parameters in RHSM configuration. 

      Additional info:

      This happens mostly when hosts are migrated from Customer Portal to Satellite. 

       

            Unassigned Unassigned
            rhn-support-msunil Manu Sunil
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: