On 07/01/2014 05:13 PM, Yedidyah Bar David wrote:
Hi all,
I was assigned to test [1], which was fixed by [2], which pointed at [3].
Most things worked as expected.
Issues I noticed:
* the table says that vdsClient with or without '-s' should work against vdsm with ssl=true or ssl=false. In my tests '-s' worked with true, without '-s' worked with false, but the other options didn't work.
"vdsClient -s" means to use secure communication, which will work properly if "ssl=true" is configured in vdsm.conf (btw, if ssl not specified there true is the default). bare in mind, that after changing the conf file you need to restart vdsmd service. when you change vdsm.conf like "ssl=true" to "ssl=false", before running vdsmd again, you need to perform "vdsm-tool configure" to configure all related service to work properly with the new vdsm configuration (in that case, not secured which require libvirtd.conf and qemu.conf update) after vdsm-tool configures libvirtd.conf and qemu.conf accordingly , you can start vdsmd and see that "vdsClient" (without -s) works properly. this works as far as I checked in vdsm 3.5
* the vdsm-tool package does not depend on vdsm, but 'vdsm-tool configure --force' fails without it.
I didn't open bugs on them because they seem insignificant.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1069636 [2] http://gerrit.ovirt.org/27298 [3] http://www.ovirt.org/Configure_libvirt_testing_matrix
-- Yaniv Bronhaim.