Show Table of Contents
7.7.3. Reregistering a Hypervisor
When a hypervisor is deleted, the deletion itself is recorded in Subscription Asset Manager as a marker. The hypervisor is prevented from re-registering with the same subscription inventory ID. If the hypervisor is added back later, it is registered with a new ID. This is why the UUID file must be deleted when the hypervisor entry is removed; if it is ever re-registered, then new host/guest mappings must be created.
If for some reason the hypervisor must be re-registered with the same UUID, then the deletion record can be removed.
[root@sam-server ~]# headpin -u admin -p admin system remove_deletion --uuid=<system uuid>
Then, the system can be re-registered using its original ID:
[root@rhel-server ~]# subscription-manager register --username admin-example --password secret --org=12345678-90 --consumerid=7d133d55-876f-4f47-83eb-0ee931cb0a97
The organization ID should be available in the Subscription Asset Manager UI or in the Portal entry for the organization. If another system is already registered to that organization, then the ID is available using the
subscription-manager orgs command.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.