Description of problem:

After provisioning a host using automation and registering to Satellite using Global Registration, the owner of the host is being incorrectly changed to a User (the one who triggered registration) instead of retaining the intended Usergroup, even though the default setting under:

Administer > Settings > Provisioning > Host owner
is explicitly configured to assign ownership to a Usergroup.
 

How reproducible:

 100%

Is this issue a regression from an earlier version:

 Yes, it was working till 6.15, after this BZ was fixed SAT-2576 it does not work.

Steps to Reproduce:

1. In Satellite Web UI:

   * Navigate to `Administer > Settings > Provisioning > Host owner`
   * Set the default to a {}Usergroup{} (e.g., `xxxxxProvisioningGroup`).

2. provision a host using automation tool and register by following the next step:-

3.  Log in as a different user (e.g., `test`) who has required roles associated to register a system and then generate the registration command using that user

4. Register the provisioned host using Global Registration:

   curl -sS 'https://<satellite_fqdn>/register?...' | bash

  

5. Observe the owner of the host post-registration.

Actual behavior:

• Host owner_type is overwritten as User, and the owner is set to the user who performed registration (test in this case).

Expected behavior:

• The host should retain the original Usergroup assigned at provisioning.

• Global Registration should respect the existing owner_type and owner when they are already set, or default to the configured Usergroup under Provisioning Settings.

Business Impact / Additional info:

- Incorrect permissions and visibility are assigned.

• Non-admin users can see or manage hosts they shouldn’t have access to.