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

Bug 1268854

Summary: [TEXT] Improve vdsm-tool register error message when UUID is missing
Product: Red Hat Enterprise Virtualization Manager Reporter: Fabian Deutsch <fdeutsch>
Component: vdsmAssignee: Douglas Schilling Landgraf <dougsland>
Status: CLOSED WORKSFORME QA Contact: Gil Klein <gklein>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.0.0CC: bazulay, dfediuck, fdeutsch, gklein, lsurette, ycui, yeylon, ykaul
Target Milestone: ovirt-4.0.0-alpha   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-03-23 13:41:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Node RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Fabian Deutsch 2015-10-05 13:05:55 UTC 
Description of problem:
$ vdsm-tool register --check-fqdn False --engine-fqdn 192.168.178.29

It is solved by doing
$ cat /proc/sys/kernel/random/uuid > /etc/vdsm/vdsm.id
before the registration

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
11:41:18,391 INFO program: 1#01110/05/2015 11:41:18 AM =======================================
11:41:18,391 INFO program: 2#01110/05/2015 11:41:18 AM Registering the node
11:41:18,391 INFO program: 3#01110/05/2015 11:41:18 AM =======================================
11:41:18,391 INFO program: 4#01110/05/2015 11:41:18 AM Received the following attributes:
11:41:18,391 INFO program: 5#01110/05/2015 11:41:18 AM Engine FQDN: 192.168.178.29
11:41:18,392 INFO program: 6#01110/05/2015 11:41:18 AM Engine URL: https://192.168.178.29
11:41:18,392 INFO program: 7#01110/05/2015 11:41:18 AM Engine https port: 443
11:41:18,392 INFO program: 8#01110/05/2015 11:41:18 AM Check FQDN: False
11:41:18,392 INFO program: 9#01110/05/2015 11:41:18 AM Fingerprint: None
11:41:18,392 INFO program: 10#01110/05/2015 11:41:18 AM Node address: None
11:41:18,392 INFO program: 11#01110/05/2015 11:41:18 AM Node name: None
11:41:18,392 INFO program: 12#01110/05/2015 11:41:18 AM SSH User: root
11:41:18,392 INFO program: 13#01110/05/2015 11:41:18 AM SSH Port: 22
11:41:18,392 INFO program: 14#01110/05/2015 11:41:18 AM VDSM Port: 54321
11:41:18,392 INFO program: 15#01110/05/2015 11:41:18 AM VDSM UUID: None
11:41:18,392 INFO program: 16#01110/05/2015 11:41:18 AM Engine CA: /etc/pki/ovirt-engine/ca.pem
11:41:18,392 INFO program: 17#01110/05/2015 11:41:18 AM Starting registration...
11:41:18,392 INFO program: 18#01110/05/2015 11:41:18 AM Get version via: https://192.168.178.29/ovirt-engine/services/host-register?version=1&command=get-version
11:41:18,392 INFO program: 19#01110/05/2015 11:41:18 AM Download CA via: https://192.168.178.29/ovirt-engine/services/host-register?version=1&command=get-pki-trust
11:41:18,393 INFO program: 20#01110/05/2015 11:41:18 AM Download SSH via: https://192.168.178.29/ovirt-engine/services/host-register?version=1&command=get-ssh-trust
11:41:18,393 INFO program: 21#01110/05/2015 11:41:18 AM Registration via: https://192.168.178.29/ovirt-engine/services/host-register?version=1&command=register&sshUser=root&sshPort=22&port=54321&uniqueId=None
11:41:18,393 INFO program: 22#01110/05/2015 11:41:18 AM Cannot connect to engine. 192.168.178.29 matches the FQDN of Engine?
11:41:18,393 INFO program: 23#011Traceback (most recent call last):
11:41:18,393 INFO program: 24#011  File "/usr/lib/python2.7/site-packages/vdsm/tool/register.py", line 477, in main
11:41:18,393 INFO program: 25#011    reg.host_uuid()
11:41:18,393 INFO program: 26#011  File "/usr/lib/python2.7/site-packages/vdsm/tool/register.py", line 275, in host_uuid
11:41:18,393 INFO program: 27#011    f.write(self.uuid)
11:41:18,393 INFO program: 28#011TypeError: expected a character buffer object
Comment 3 Fabian Deutsch 2016-03-23 13:41:49 UTC 
There does not seem to be a problem around this.