Consolidated Troubleshooting Article for Red Hat Satellite 6.x Client Subscription Issues

Subscription-manager Issues

• Why re-registering a host or a capsule to Satellite fails with error "Validation failed: Puppet Capsule does not have the Puppet feature, Puppet ca Capsule does not have the Puppet CA feature (HTTP error code 422: Unprocessable Entity)"?
• Host is not associated with the respective capsule location when registered with subscription-manager register command
• Unable to register client with Red Hat Satellite 6 due to 'Validation failed: Name must not include periods' error
• subscription-manager register command fails with error [Errno 110] Connection timed out on Red Hat Satellite 6
• How to register multiple Content Hosts with same UUID to Red Hat Satellite 6?
• Host registration with Red Hat Satellite fails with error 502 timeout
• When attempting to register a system to Red Hat Satellite or Capsule, the subscription-manager registration process may fail with a "Network error, unable to connect to server" message.
• RHEL 8 systems with OSPP applied cannot install katello-ca-consumer package from Satellite
• Red Hat Satellite Client Registration failing with Couldn't Find Host error
• [Satellite 6] Host registration fails with: Runtime Error could not obtain pessimistic lock at org.postgresql.core
• subscription-manager commands fail with the error message: "Unable to verify server's identity: tlsv1 alert unknown ca"
• Registering/provisioning a Content Host to/from an external capsule shows "Unable to verify server's identity: sslv3 alert bad certificate error"
• Satellite 6 : Unable to register client with Activation key which is associated with a host collection
• Unable to register systems to Satellite : "Unable to register system, not all services available"
• Not able to register a host to Satellite 6.2 : Unable to register system, not all services available
• System registration fails with error System certificates corrupted. Please reregister on content host registering to Red Hat Satellite 6
• Host registration with Red Hat Satellite is failing with the error Validation failed.
• Host registration or subscription-manager refresh command failed with "400 - Bad Request" after upgrade to Red Hat Satellite 6.8.5
• Registering system to Red Hat Satellite 6 returns "No such environment" error.
• Registering a machine with Red Hat Satellite 6.6 fails with error HTTP error (422 - Unknown): Validation failed: Attached to can't be blank
• This content is not included.Subscription-manager fails with "certificate verify failed (_ssl.c:618)" when registering systems to Red Hat Satellite Capsule.
• "HTTP error (422 - Unknown): Validation failed: Ip does not match selected subnet" error while registering system to Satellite 6
• Registering a host fails with unknown or not assigned environment id 1
• Host registration via bootstrap.py script to the Red Hat Satellite Server fails with error: An error occured: HTTP Error 422: Unprocessable Entity
• Registering new servers to the Red Hat Satellite 6 fails with error "Remote server error. Please check the connection details, or see /var/log/rhsm/rhsm.log for more information".
• Why does subscription-manager return a non-zero exit code and display "Unable to find available subscriptions for all your installed products" during an otherwise successful registration to a Satellite where Simple Content Access is in use?
• Red Hat Enterprise Linux (RHEL) Workstation installed in Azure, AWS or GCP show as Partially Entitled in Satellite
• Certificate issue while registering the RHEL 6 content host with Red Hat Satellite 6 server.
• Clients are unable to connect with the Red Hat Satellite 6 server due to recent expired AddTrust Root CA certificates.
• Registration on Satellite 6 fails when RHEL 8 client has FIPS with a FUTURE crypto policy enabled
• Issue while registering RHEL8.2 client with Red Hat Satellite server
• [Satellite6] Registering a new VM to Satellite fails with "Guest's host does not match owner of pool" error
• [Satellite 6.x] subscription-manager register command fails with HTTP error (400 - Bad Request): Problem creating unit ConsumerDTO [uuid: 99b8a0c0-016c-4c00-92bb-250c2a49ade7, name: hostname, owner id: null]
• subscription-manager register command fails with HTTP error (400 - Bad Request): Problem creating unit ConsumerDTO [uuid: null, name: hostname, owner id: null]
• How to register Red Hat Enterprise Linux Desktop to Red Hat Satellite 6
• Register content host using activation key failed to attach Red Hat Enterprise Linux for Virtual Datacenters subscription
• Registering the system using subscription-manager fails with Unable to find available subscriptions for all your installed products.
• In Red Hat Satellite 6 Content Host re-registration fails with error an "Organization does not exist" and "Remote server error. Please check the connection details, or see /var/log/rhsm/rhsm.log for more information".
• Any Subscription-manager command throws Error: System certificates corrupted. Please reregister.

Issues related to Global Subscription Template

• Location not taken into account when registering a new client on Satellite using Global Registration Script
• Registering host to Red Hat Satellite 6 using Global Registration Template fails with ERROR: unauthorized
• Registering a host with non-English locale using Satellite's Global Registration Template fails with a Host was not found by the subscription UUID: '' error

Yum Issues

• Yum transaction on Red Hat Satellite client reports error [Errno 14] HTTPS Error 500 - Internal Server Error
• Client hosts connected to Red Hat Satellite server shows package count as 0
• 'yum update' fails to update third party packages after enabling SCA with "none of the providers can be installed"
• dnf/yum command gives package conflict or none of the providers can be installed error
• Installation of the 'xorg-x11-drv-nvidia-470xx-cuda' rpm fails with "All matches were filtered out by modular filtering for argument: xorg-x11-drv-nvidia-470xx-cuda" error
• Yum transactions on Satellite clients are slowed down by entitlement related messages after enabling Simple Content Access on Red Hat Satellite.
• Why does yum fail with error Peer's certificate issuer has been marked as not trusted by the user?
• [Errno 14] curl#60 - "Peer's certificate issuer has been marked as not trusted by the user."
• Errors returned with yum check-update indicating broken update notices

How To

• How do I register a system to Red Hat Satellite 6 server?
• How to register a cloned virtual machine on the satellite server?
• Using an Ansible playbook with the Global Registration method to register hosts to Red Hat Satellite 6.x

Q&A

• Which RHEL versions and architectures are supported as client systems managed by Red Hat Satellite server?
• Why there is an Exclamation mark in front of repositories id when running yum on clients registered with Red Hat Satellite 6?
• What is the difference between Repo-pkgs and Repo-available-pkgs?

Useful Information

• Red Hat Satellite 6 Feature Overview: Registering Hosts using the Global Registration method