[Satellite6] Registering a new VM to Satellite fails with "Guest's host does not match owner of pool" error

Solution Verified - Updated

Environment

Red Hat Satellite or Proxy 6.0

Issue

  • having multiple datacenters with guests provisioned from Satellite6
  • registering guests from some datacenter fails with "Guest's host does not match owner of pool" error

Resolution

  • Remove guest subscription from activation key
  • On the guest, run subscription-manager register --org=org_name --activation-key=key
  • In Satellite6 WebUI: Content Host -> find the guest
  • Click through Virtual Host
  • Add VDC subscription to that hypervisor
  • Go back to guest in Sat6 Web UI
  • Add Unlimited subscription
  • On the guest: subscription-manager refresh

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

This happens when an unlimitted subscription is put into an activation key and then the activation key is tried to be used on a guest from a different hypervisor.

Activation keys are full templates at the moment: every subscription in them must be successfully attached at registration, otherwise the registration fails. So one cannot put a guest subscription from hypervisor A into an activation key for hypervisor B guest.

The proper provisioning scheme to follow is to have one activation key per one hypervisor.

Note that This content is not included.this RFE will make the user experience better in these situations.

Diagnostic Steps

subscription-manager fails with:

# subscription-manager register --org="MyOrg" --activationkey="ActKey"
Guest's host does not match owner of pool: '8a41a8954d7afa6c014d7c7848240e01'.

/var/log/candlepin/candlepin.log having:

/candlepin/activation_keyts/act_key
...the hex string appears to be the activation key to candlepin
[...]
POST /candlepin/environments/2-3/consumers/?activation_keys=new_string
Entitlement not granted: [virt.guest.host.does.not.match.pool.owner]
Response: status=403
SBR
Product(s)
Components
Category
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.