Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After delete profiles in /var/lib/virt-who/, restart virt-who will generate two same hypervisors in satelite webUI.
Version-Release number of selected component (if applicable):
virt-who-0.18-1.el6.noarch
subscription-manager-1.18.6-1.el6.x86_64
python-rhsm-1.18.6-1.el6.x86_64
Satellite5.7
How reproducible:
Always
Steps to Reproduce:
1. Configure virt-who run at esx mode and send host/guest association to satellite5.7, virt-who send two esx hypervisor to satellite5.7
[root@hp-z220-05 virt-who]# virt-who --satellite --satellite-server=satellite57jan3.redhat.com --satellite-username=admin --satellite-password=redhat --esx --esx-server=10.73.3.161 --esx-username=Administrator --esx-password=Welcome1! -o -d
2. Go to satellite5.7 webUI, it will show two different hypervisors under "system" tab
"58a14d56-558b-61d0-fbdf-b690cf7255df"
"9fea4d56-5ed5-ddfe-b806-e7872726c0d7"
3. Check the profiles under the /var/lib/virt-who
[root@hp-z220-05 virt-who]# ll /var/lib/virt-who/
total 8
-rw-rw-rw-. 1 root root 1678 Jan 4 22:40 hypervisor-systemid-58a14d56-558b-61d0-fbdf-b690cf7255df
-rw-rw-rw-. 1 root root 1678 Jan 4 22:40 hypervisor-systemid-9fea4d56-5ed5-ddfe-b806-e7872726c0d7
4. Delete the profiles under the /var/lib/virt-who
[root@hp-z220-05 virt-who]# rm -rf /var/lib/virt-who/*
5. Rerun virt-who again as step1. check virt-who's log, it has send host/guest mapping info to satellite5.7 successfully.
[root@hp-z220-05 virt-who]# virt-who --satellite --satellite-server=satellite57jan3.redhat.com --satellite-username=admin --satellite-password=redhat --esx --esx-server=10.73.3.161 --esx-username=Administrator --esx-password=Welcome1! -o -d
6. Go to satellite5.7 webUI, Check hypervisors under the "system" tab.
Actual results:
It will show two same hypervisor items in the webUI. please see screenshot in attachment hypervisors.jpeg
Expected results:
It should show same hypervisor once in satellite webUI.
Additional info:
So far I know virt-who creates the profiles in Sat5. Sat5 cannot influence, what API calls are called by virt-who. If virt-who creates two profiles, there are two profiles in Sat5. Expected behavior from Sat5 POV.
I'm re-assigning to virt-who.
The data stored in /var/lib/virtwho/hypervisor-systemid-* files are the system certificates returned from satellite registration. Deleting these files is akin to unregistering the machine from satellite, and therefore their original profiles should be deleted in satellite.
After deletion of this file, there is simply no way to re-associate the system with the existing profile in satellite, so we must make a new one. Please don't delete the files under /var/lib/virtwho without having backups.