After taking F2F with Eyal S. we saw there is still another issue here the OVF fails in a specific scenario (see below) and still the SD is deactivated. So original Disregard scenario about as it is not relevant anymore. New scenario: 1) UI: Create a new SD (NFS preferred) with a VM . 2) UI: To make sure OVF update will be triggered change the VM name . 3) VDSM host: change the relevant SD images on (rhev/data/...) user &group ownership from kvm:vdsm (or 36:36) to root:root via : "chwon root:root <image_path>" 4) Deactivate relevant SD . We saw the OVF update failed but still the SD was deactivated.
The following scenario has been tested: **************** New scenario: 1) UI: Create a new SD (NFS preferred) with a VM . 2) UI: To make sure OVF update will be triggered change the VM name . 3) VDSM host: change the relevant SD images on (rhev/data/...) user &group ownership from kvm:vdsm (or 36:36) to root:root via : "chwon root:root <image_path>" 4) Deactivate relevant SD . We saw the OVF update failed but still the SD was deactivated. ****************** The results are: 1. When checking the "Ignore OVF update failure" checkbox: the OVF is ignored and the SD is deactivated. 2. When NOT checking the "Ignore OVF update failure" checkbox: the OVF update fails and the SD stays active. Moving to VERIFIED
This bugzilla is included in oVirt 4.2.1 release, published on Feb 12th 2018. Since the problem described in this bug report should be resolved in oVirt 4.2.1 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.