Our python code interfacing with vdsm should use its api and not run vdsClient. This will allow in principle simpler code (no need to parse output), faster execution (do not run an external program) etc.
vdsClient was used up until now because it was somewhat simpler to debug and because in the past there were some issues using the api in certain cases.
I am currently opening this bug due to an expected breakage caused by future fixing of bug #1005923 . This breakage can (obviously) be solved in other ways (including asking vdsm to add an option '--force' or something like that), but it seems that moving to use only the api is the better approach in the long run.
Since there will be a breakage, this will be a blocker if bug #1005923 will be targeted to 3.5.0
Automated message: can you please update doctext or set it as not required?
Hi, Sandro what the best way to verify this bug, I believe we just need to run different deployment cases and check that all work fine?
Yes Artyom, just executing deployment test cases should expose errors in the migration from vdsClient to vdsm API
Verified on ovirt-hosted-engine-setup-1.3.0-1.el7ev.noarch
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.