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 hypervisors in satellite5.X webUI, virt-who can't send host/guest mapping info to server
Version-Release number of selected component (if applicable):
virt-who-0.16-8.el6.noarch
subscription-manager-1.16.8-8.el6.x86_64
python-rhsm-1.16.6-1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Configure virt-who run at esx mode and send mapping info to satellite5.7
[root@hp-xw9400-01 ~]# cat /etc/virt-who.d/virt
[test-esx1]
type=esx
server=10.73.2.95
username=Administrator
#encrypted_password=07928b0a0b0caa7c6e3b5915466210bd
password=Welcome1!
owner=ACME_Corporation
env=Library
sat_server=ibm-x3650-05.ovirt.rhts.eng.bos.redhat.com
sat_username=admin
sat_password=redhat
2. Restart virt-who service and check virt-who's log.virt-who send host/guest mapping info to satellite5.X
3. Go to satellite WebUI-->System tab, delete hypervisor in webUI
4. Restart virt-who service again and check virt-who's log.
...................................................
...................................................
2016-04-08 22:41:25,589 [virtwho.main ERROR] MainProcess(15245):MainThread @satellite.py:hypervisorCheckIn:173 - Unable to send host/guest association to the satellite:
Traceback (most recent call last):
File "/usr/share/virt-who/manager/satellite/satellite.py", line 171, in hypervisorCheckIn
self.server.registration.virt_notify(hypervisor_systemid["system_id"], plan)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1253, in request
return self._parse_response(h.getfile(), sock)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1392, in _parse_response
return u.close()
File "/usr/lib64/python2.6/xmlrpclib.py", line 838, in close
raise Fault(**self._stack[0])
Fault: <Fault -9: '\nError Message:\n Please run rhn_register as root on this client\nError Class Code: 9\nError Class Info: Invalid System Credentials.\nExplanation: \n An error has occurred while processing your request. If this problem\n persists please consult the Red Hat Customer Portal Knowledge Base\n landing page on common registration Error Class Codes at\n https://access.redhat.com/solutions/17036 for a possible resolution.\n If you choose to open a support case in the Red Hat Customer Portal,\n please be sure to include details of what you were trying to do when\n this error occurred and specifics on how to reproduce this problem.\n'>
2016-04-08 22:41:25,590 [virtwho.main ERROR] MainProcess(15245):MainThread @virtwho.py:send:203 - Unable to send data: Unable to send host/guest association to the satellite: <Fault -9: '\nError Message:\n Please run rhn_register as root on this client\nError Class Code: 9\nError Class Info: Invalid System Credentials.\nExplanation: \n An error has occurred while processing your request. If this problem\n persists please consult the Red Hat Customer Portal Knowledge Base\n landing page on common registration Error Class Codes at\n https://access.redhat.com/solutions/17036 for a possible resolution.\n If you choose to open a support case in the Red Hat Customer Portal,\n please be sure to include details of what you were trying to do when\n this error occurred and specifics on how to reproduce this problem.\n'>
2016-04-08 22:41:25,591 [virtwho.main DEBUG] MainProcess(15245):MainThread @virtwho.py:send_report:168 - Report from "test-esx1" failed to sent
5, Go to /var/lib/virt-who, check content in this directory.
[root@cisco-e160dp-01 virt-who]# pwd
/var/lib/virt-who
[root@cisco-e160dp-01 virt-who]# ll
total 16
-rw-rw-rw-. 1 root root 1671 Apr 11 08:38 hypervisor-systemid-3e504d56-3982-037b-f3e6-669289892fa1
-rw-rw-rw-. 1 root root 1673 Apr 11 08:36 hypervisor-systemid-54776896-82e3-4a2e-b9fa-62425b5457a6
-rw-rw-rw-. 1 root root 1671 Apr 11 08:38 hypervisor-systemid-7a384d56-085c-0e32-c7ad-f7181c3f6ddf
-rw-rw-rw-. 1 root root 1673 Apr 11 08:36 hypervisor-systemid-df53a779-d8dd-4418-9af2-7525b58690b5
Actual results:
It will show some error info in virt-who's log, virt-who can't send host/guest mapping info to satellite5.X
Expected results:
It shouldn't show any error info in virt-who's log, virt-who still can send mapping info to satellite5.X after delete hypervisor in satellite5.X webUI.
Additional info:
Description of problem: After delete hypervisors in satellite5.X webUI, virt-who can't send host/guest mapping info to server Version-Release number of selected component (if applicable): virt-who-0.16-8.el6.noarch subscription-manager-1.16.8-8.el6.x86_64 python-rhsm-1.16.6-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Configure virt-who run at esx mode and send mapping info to satellite5.7 [root@hp-xw9400-01 ~]# cat /etc/virt-who.d/virt [test-esx1] type=esx server=10.73.2.95 username=Administrator #encrypted_password=07928b0a0b0caa7c6e3b5915466210bd password=Welcome1! owner=ACME_Corporation env=Library sat_server=ibm-x3650-05.ovirt.rhts.eng.bos.redhat.com sat_username=admin sat_password=redhat 2. Restart virt-who service and check virt-who's log.virt-who send host/guest mapping info to satellite5.X 3. Go to satellite WebUI-->System tab, delete hypervisor in webUI 4. Restart virt-who service again and check virt-who's log. ................................................... ................................................... 2016-04-08 22:41:25,589 [virtwho.main ERROR] MainProcess(15245):MainThread @satellite.py:hypervisorCheckIn:173 - Unable to send host/guest association to the satellite: Traceback (most recent call last): File "/usr/share/virt-who/manager/satellite/satellite.py", line 171, in hypervisorCheckIn self.server.registration.virt_notify(hypervisor_systemid["system_id"], plan) File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request verbose=self.__verbose File "/usr/lib64/python2.6/xmlrpclib.py", line 1253, in request return self._parse_response(h.getfile(), sock) File "/usr/lib64/python2.6/xmlrpclib.py", line 1392, in _parse_response return u.close() File "/usr/lib64/python2.6/xmlrpclib.py", line 838, in close raise Fault(**self._stack[0]) Fault: <Fault -9: '\nError Message:\n Please run rhn_register as root on this client\nError Class Code: 9\nError Class Info: Invalid System Credentials.\nExplanation: \n An error has occurred while processing your request. If this problem\n persists please consult the Red Hat Customer Portal Knowledge Base\n landing page on common registration Error Class Codes at\n https://access.redhat.com/solutions/17036 for a possible resolution.\n If you choose to open a support case in the Red Hat Customer Portal,\n please be sure to include details of what you were trying to do when\n this error occurred and specifics on how to reproduce this problem.\n'> 2016-04-08 22:41:25,590 [virtwho.main ERROR] MainProcess(15245):MainThread @virtwho.py:send:203 - Unable to send data: Unable to send host/guest association to the satellite: <Fault -9: '\nError Message:\n Please run rhn_register as root on this client\nError Class Code: 9\nError Class Info: Invalid System Credentials.\nExplanation: \n An error has occurred while processing your request. If this problem\n persists please consult the Red Hat Customer Portal Knowledge Base\n landing page on common registration Error Class Codes at\n https://access.redhat.com/solutions/17036 for a possible resolution.\n If you choose to open a support case in the Red Hat Customer Portal,\n please be sure to include details of what you were trying to do when\n this error occurred and specifics on how to reproduce this problem.\n'> 2016-04-08 22:41:25,591 [virtwho.main DEBUG] MainProcess(15245):MainThread @virtwho.py:send_report:168 - Report from "test-esx1" failed to sent 5, Go to /var/lib/virt-who, check content in this directory. [root@cisco-e160dp-01 virt-who]# pwd /var/lib/virt-who [root@cisco-e160dp-01 virt-who]# ll total 16 -rw-rw-rw-. 1 root root 1671 Apr 11 08:38 hypervisor-systemid-3e504d56-3982-037b-f3e6-669289892fa1 -rw-rw-rw-. 1 root root 1673 Apr 11 08:36 hypervisor-systemid-54776896-82e3-4a2e-b9fa-62425b5457a6 -rw-rw-rw-. 1 root root 1671 Apr 11 08:38 hypervisor-systemid-7a384d56-085c-0e32-c7ad-f7181c3f6ddf -rw-rw-rw-. 1 root root 1673 Apr 11 08:36 hypervisor-systemid-df53a779-d8dd-4418-9af2-7525b58690b5 Actual results: It will show some error info in virt-who's log, virt-who can't send host/guest mapping info to satellite5.X Expected results: It shouldn't show any error info in virt-who's log, virt-who still can send mapping info to satellite5.X after delete hypervisor in satellite5.X webUI. Additional info: