Description of problem: The uploader requires existence of user 'vdsm' on the machine where its executed. Its rpm doesn't check/add the required user, so if that user doesn't exist on the machine where it runs - the uploader fails.(for example - ovirt-engine machine where the engine was built from source and doesn't require user vdsm to exist) The error at failure: "ERROR: A user named vdsm with a UID and GID of 36 must be defined on the system to mount the export storage domain on myexport as Read/Write" Version-Release number of selected component (if applicable): 3.4 How reproducible: when user vdsm doesn't exist on the machine where the uploader runs. Expected results: either there's no need to have user 'vdsm' or the uploader adds it upon installation. Additional info:
Lev, you can find examples for checking user and group existence and code for creating them within the spec file in vdsm and ovirt-engine projects spec files.
Please clone the BZ to iso uploader for tracking it too.
(In reply to Sandro Bonazzola from comment #2) > Please clone the BZ to iso uploader for tracking it too. Can't do - there is no ovirt-iso-uploader component in oVirt. And since the patch is basically the same I think it's OK to track both in one bug.
ok, ovirt-image-uploader-3.5.0-0.1.master.20140905074913.git9639d6c.el6.noarch
oVirt 3.5 has been released and should include the fix for this issue.