3.15. Registration Issues

This section describes known issues with the Satellite 6.1 Registration component.
BZ 1199408: Non-admin user cannot register content host
Issue

If you create a non-admin user account, even with the required permissions for registering Content Hosts, any attempt to register a host fails. For example: 

# subscription-manager register --org="platops" --environment="Library"
Username: jdoe
Password:
undefined local variable or method `anonymous_admin' for #<User:0x00000009734318>
This issue appears to be the result of an incorrect method call (allowed_organization method is trying to call anonymous_admin as an instance method, but anonymous_admin is actually a class method).
Workaround

To work around this issue, ensure the user is assigned the Admin role, or use an Activation Key.

BZ 1135557: Registering a large number of clients in parallel results in some hosts showing up in Satellite 6 and subscription-manager reporting errors
Issue

Satellite 6 and the subscription-manager client show inconsistencies when registering many clients in parallel (for example, 50, 100, 150, 200), using an activation key.

It has been observed that while attempting to register 100 clients at the same time, Satellite 6 reports 100 new content hosts in the web UI and in the candlepin database (table cp_consumers), but the output from rhsm on the clients shows errors and timeouts.
Workaround

If you run subscription-manager register using an activation key and observe a failure, follow these steps:

  1. Open the /var/log/rhsm/rhsm.log file on the client and search for the error that occurred during registration.
  2. If the error is an SSLTimeoutError, request the Satellite 6 administrator to confirm if the client has been registered. Navigate to Hosts → Content Hosts and look for the client to make this confirmation.