Location not taken into account when registering a new client on Satellite using Global Registration Script

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.10+

Issue

  • After registering a new Satellite client ends up with the default location.
  • Host registers to incorrect location even after generating Global Registration Script with correct location in Satellite.

Resolution

  • This issue is known by Red Hat and tracked in This content is not included.SAT-22131

  • In the mean time as a workaround, the CA of the Satellite needs to be trusted before running the registration script, it can be done by either:

    1. Use a trusted Certificate Authority to sign the Satellite/Capsules certificates
    2. Trusting the Satellite CA: #6955903

For more KB articles/solutions related to Red Hat Satellite 6.x Client Subscription Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Client Subscription Issues

Root Cause

In the current registration script, insecure mode is not handled for Location part of the script.

SBR
Product(s)
Components
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.