This commit alters the behavior of registering a content host (with or without an activation key) that is to be associated with a foreman host to do the following:
1. identify the foreman host that this content host will be associated with by both name and mac address (previously it was only by name) 2. if the foreman host identified is already associated with a content host, delete it and then create/associate a new one. (This will avoid there becoming duplicate content hosts with the same name.)
Related issues
Bug #7005: Unable to delete host tied back to activation key
Added by Brad Buckingham almost 10 years ago
fixes #7005 / BZ 1122736 - content host - change registration behavior with foreman host
This commit alters the behavior of registering a content host
(with or without an activation key) that is to be associated
with a foreman host to do the following:
1. identify the foreman host that this content host will be
associated with by both name and mac address (previously
it was only by name)
2. if the foreman host identified is already associated with a
content host, delete it and then create/associate a new one.
(This will avoid there becoming duplicate content hosts with
the same name.)