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:
When virt-who run at rhevm mode, virt-who will send the host's defined name other than real hostname to satellite
Version-Release number of selected component (if applicable):
Satellite6.2.7
virt-who-0.17-10.el6sat.noarch
rhevm3.6.10.2-0.2.el6
How reproducible:
Always
Steps to Reproduce:
1. Configure virt-who run at rhevm mode and send host's hostname to satellite
[root@hp-z220-13 virt-who.d]# cat /etc/virt-who.d/rhevm
[test-rhevm1]
type=rhevm
server=https://ibm-hs22-04.lab.bos.redhat.com:443
username=admin@internal
password=redhat
owner=org1
env=Library
rhsm_username=admin
rhsm_password=admin
rhsm_hostname=hp-bl460cg5-01.rhts.eng.bos.redhat.com
rhsm_port=443
rhsm_prefix=/rhsm
rhsm_proxy_hostname=aaaa
hypervisor_id=hostname
2. In rhevm webUI, register two hosts to rhevm, the first one's hostname is hp-z220-05.qe.lab.eng.nay.redhat.com and the other one is hp-z220-13.qe.lab.eng.nay.redhat.com
[root@hp-z220-05 yum.repos.d]# hostname
hp-z220-05.qe.lab.eng.nay.redhat.com
[root@hp-z220-13 yum.repos.d]# hostname
hp-z220-13.qe.lab.eng.nay.redhat.com
3. In rhevm webUI, Update the hp-z220-05.qe.lab.eng.nay.redhat.com's name to "test_name", please see screenshot in attachment update_hostname.jpeg
4. Restart virt-who service and check virt-who's log.
[root@hp-z220-13 yum.repos.d]# service virt-who restart && tail -f /var/log/rhsm/rhsm.log
[root@hp-z220-13 virt-who.d]# service virt-who restart
Stopping virt-who: [ OK ]
Starting virt-who: [ OK ]
2017-01-12 19:54:53,093 [virtwho.main DEBUG] MainProcess(9958):MainThread @subscriptionmanager.py:hypervisorCheckIn:195 - Host-to-guest mapping: {
"hp-z220-13.qe.lab.eng.nay.redhat.com": [
{
"guestId": "aa8dc538-61ef-4742-88db-fdbce9a97641",
"state": 1,
"attributes": {
"active": 1,
"virtWhoType": "rhevm"
}
}
],
"test_name": [] ====> It's the defined name
}
Actual results:
Virt-who send host's defined name to satellite.
Expected results:
Virt-who should send the real hostname to satellite other than defined name. in the example, virt-who should send "hp-z220-05.qe.lab.eng.nay.redhat.com" other than "test_name" to satellite.
Additional info: