CURRENT IMPLEMENTATION vdsm-upgrade part of vdsm-reg use ovirt-node specific logic to trigger node upgrade. PROBLEMS IN CURRENT IMPLEMENTATION node upgrade should have nothing to do with vdsm, it should be part of ovirt-node. ovirt-node has its own tool now, see bug#858596. NEW IMPLEMENTATION Rewrite vdsm-upgrade as a wrapper script to ovirt-node-upgrade tool, keep interface to engine. EXPECTED RESULT Engine indirectly use ovirt-node-upgrade tool, ovirt-node specific code is removed from vdsm-upgrade.
oVirt 3.5 has been released and should include the fix for this issue.