Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1188529

Summary: libvirt to Satellite: invalid literal for long() with base 16
Product: Red Hat Satellite 5 Reporter: Jan Hutař <jhutar>
Component: APIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DEFERRED QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 570   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-09 12:26:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1127217    

Description Jan Hutař 2015-02-03 07:01:57 UTC
Description of problem:
I have RHEL7 libvirt host with virt-who installed and Satellite 5.7 on a different system. Running virt-who produces traceback:


Version-Release number of selected component (if applicable):
Host: virt-who-0.11-5.el7.noarch
      libvirt-1.2.8-16.el7.x86_64
Satellite: Satellite-5.7.0-RHEL6-re20150108.2-x86_64


How reproducible:
tried on one host only, always


Steps to Reproduce:
1. Have Satellite 5.7.0
2. Have libvirtd host with some guests
3. # virt-who --one-shot --libvirt --satellite --satellite-server=<satellite_fqdn> --satellite-username=<satellite_user> --satellite-password=<satellite_pass> --libvirt-server=qemu:// -d


Actual results:
It fails with:
Traceback (most recent call last):
  File "/usr/share/virt-who/manager/satellite/satellite.py", line 160, in hypervisorCheckIn
    self.server.registration.virt_notify(hypervisor_systemid["system_id"], plan)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1578, in __request
    verbose=self.__verbose
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request
    return self.single_request(host, handler, request_body, verbose)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1297, in single_request
    return self.parse_response(response)
  File "/usr/lib64/python2.7/xmlrpclib.py", line 1473, in parse_response
    return u.close()
  File "/usr/lib64/python2.7/xmlrpclib.py", line 793, in close
    raise Fault(**self._stack[0])
Fault: <Fault 1: 'While running \'registration.virt_notify\': caught\n<type \'exceptions.ValueError\'> : invalid literal for long() with base 16: "{\'guestId\': \'14519fb3c89c4f0fb40d52dab95178d1\', \'attributes\': {\'active\': 1, \'virtWhoType\': \'libvirt\', \'hypervisorType\': \'QEMU\'}, \'state\': 1}"\n'>


Expected results:
Should work


Additional info:
I have not seen the issue when I did this before I have installed some guests

Comment 4 Radek Novacek 2015-02-03 07:28:04 UTC
This is a server-side fault in satellite 5. I'll change the component to Satellite 5 for further investigation. If virt-who sends some incorrect data, please reassign it back to virt-who.

Comment 5 Tomas Lestach 2018-04-09 12:26:40 UTC
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog.

This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. 

Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.