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

Failure during registration appears as successful

XMLWordPrintable

    • Moderate
    • Yes

      Description of problem:

      While trying to register a bunch of systems using Ansible, I've found several systems that appear to register successfully (return code 0) but that don't succeed.

      The Ansible script pushes a .sh file like this:

      ~~~

      1. cat clients_host-registration.sh
        curl -sS --insecure 'https://$SAT_URL/register?activation_keys=AK_RHEL8&force=true&organization_id=1&setup_remote_execution_pull=true' -H 'Authorization: Bearer $AUTH_KEY' | bash
        ~~~

      And executes it and fails if its return code is different than 0.

      In this case, the output was:

      ~~~

      1. cat registration.log
        #
      2. Running registration
        #
        This system is currently not registered.
        All local data removed
        Updating Subscription Management repositories.
        Unable to read consumer identity

      This system is not registered with an entitlement server. You can use subscription-manager to register.

      No match for argument: katello-ca-consumer*
      No packages marked for removal.
      Dependencies resolved.
      Nothing to do.
      Complete!
      Updating Subscription Management repositories.
      Unable to read consumer identity

      This system is not registered with an entitlement server. You can use subscription-manager to register.

      Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".
      The system has been registered with ID: aea643af-0aa5-48a9-9267-424ed15b08ad
      The registered system name is: containerhost-1-container56.red.ddns.perf.redhat.com

      1. Running [containerhost-1-container56.red.ddns.perf.redhat.com] host initial configuration
        /usr/sbin/restorecon
        Starting deployment of REX pull provider
        could not obtain a connection from the pool within 5.000 seconds (waited 5.005 seconds); all pooled connections were in use (HTTP error code 500: Internal Server Error)
        Host [containerhost-1-container56.red.ddns.perf.redhat.com] initial configuration failed
        (23) Failed writing body
        ~~~

      Version-Release number of selected component (if applicable):

      Satellite 6.13.0 snap 12.0

      How reproducible:

      It's happened in several systems while stressing concurrent registrations.

      Steps to Reproduce:
      1. Try to register lots of systems.
      2. Look for failures.
      3.

      Actual results:

      Some of the hosts fail to register but succeed from the Ansible point of view (the bash script returns 0).

      Expected results:

      A fail registration shouldn't return 0.

      Additional info:

              jira-bugzilla-migration RH Bugzilla Integration
              jira-bugzilla-migration RH Bugzilla Integration
              Sam Bible Sam Bible
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: