Bug 560636

Summary: error during rhn_register of virtual machine without uuid
Product: [Retired] Red Hat Network Reporter: Miroslav Suchý <msuchy>
Component: RHN/BackendAssignee: Bryan Kearney <bkearney>
Status: CLOSED NOTABUG QA Contact: Red Hat Network Quality Assurance <rhn-qa-list>
Severity: medium Docs Contact:
Priority: low    
Version: rhn512CC: acarter, mhlavink, rhn-bugs
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 543509 Environment:
Last Closed: 2010-02-01 14:14:48 UTC Type: ---
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: 543509    
Bug Blocks: 543511, 559485    

Description Miroslav Suchý 2010-02-01 13:27:33 UTC
You may want to apply fix from this bug as well.

+++ This bug was initially created as a clone of Bug #543509 +++

Created an attachment (id=375451)
Traceback

Description of problem:
When you try to rhn_register qemu machine, which do not have uuid. You get traceback on server and registration will fail.

Version-Release number of selected component (if applicable):


How reproducible:
several time

Steps to Reproduce:
1.  lshal  |grep smbios.system.uuid
smbios.system.uuid = 'Not Settable'  (string)
If you have there some number, grab another virtual machine, this is prerequisity.
2. rhn_register
  
Actual results:
error

Expected results:
you will be registered

Additional info:

--- Additional comment from msuchy on 2009-12-02 10:16:24 EST ---

Solution is to replace:
  uuid_as_number = string.atol(uuid, 16)
with:
  if uuid == 'Not Settable':
      uuid_as_number = 0
  else:
      uuid_as_number = string.atol(uuid, 16)

--- Additional comment from msuchy on 2009-12-07 07:52:40 EST ---

commited as 7cdd2dd93f7fe05da6aab3e8b104bb3aa0d23801

Comment 1 Miroslav Suchý 2010-02-01 14:14:48 UTC
Scratch this. We should catch this case in client tools and not send it at all.