Bug #15197: Duplicate entries for hypervisors after renaming content host - Katello - Foreman

Actions

Copy link

Bug #15197

closed

Duplicate entries for hypervisors after renaming content host

Added by Thomas McKay over 8 years ago. Updated over 6 years ago.

Status:

Closed

Priority:

High

Assignee:

Thomas McKay

Category:

Hosts

Target version:

Katello 3.1.0

Difficulty:

Triaged:

Bugzilla link:

1340088

Pull request:

https://github.com/Katello/katello/pull/6076

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1340088
Description of problem:
After renaming the hypervisor in /content_hosts and another run of virt-who
the hypervisor content host is again created with a random name but with
the same uuid.

Version-Release number of selected component (if applicable):
Satellite 6.2 SNAP 13.1
virt-who 0.14-9.el7

How reproducible:
With every virt-who run

Steps to Reproduce:
1. Register hypervisor via virt-who
2. Rename hypervisor in /content_hosts
3. Run virt-who again

Actual results:
A new entry is created in /content_hosts

Expected results:
Only update the already existing content host

Additional info:
- virt-who is always sending the correct hypervisor uuid
- looks like the unique identifier was changed from the content hosts uuid to the name
- this is a regression as it worked fine in 6.1