Description of problem: Currently when a storage domain is deactivated we attempt to update its ovf stores. If the ovf update fails the domain will still be deactivated, in some cases we'd like to fail if the ovf update fails. Steps to Reproduce: 1. Create a NFS Storage Domain 2. Attach the domain to DC with version 3.5 and up 3. Activate the domain 4. Deactivate the domain 5. Ovf update should be executed for the domain and create ovf stores 6. Delete the images of the ovf stores from the storage 7. Activate the domain 8. deactivate the domain Actual results: The domain deactivation will succeed always Expected results: We might want to fail the deactivation when the ovf stores aren't updated Additional info:
Tested with the following code: -------------------------------- ovirt-engine-4.2.0-0.6.el7.noarch vdsm-4.20.9-1.el7ev.x86_64 Tested with following scenario: -------------------------------- Steps to Reproduce: 1. Create a NFS Storage Domain 2. Attach the domain to DC with version 3.5 and up 3. Activate the domain 4. Deactivate the domain 5. Ovf update should be executed for the domain and create ovf stores 6. Delete the images of the ovf stores from the storage ( I did this by accessing the nfs domain, and deleted the 2 images using "rm -rf" from: /mnt/kev369/ea995f89-bc02-4822-8fec-ac78dfcd767d/images/ 7. Activate the domain 8. deactivate the domain - the images were created again Not sure what the result should have been here as I expected the deactivation to fail
Hi Kevin, This bug depends on 1523225. The steps to reproduce are: 1) Create a new SD (NFS preferred) with a VM and disk base on it. 2) To make sure OVF update will be triggered, change the VM name. 3) On the VDSM host: change the relevant SD images on (rhev/data/...) user & group ownership from kvm:vdsm (or 36:36) to root:root via : "chwon -R root:root <image_path>" 4) Deactivate relevant SD. Expected result: The OVf update should fail and cause the deactivation to failed. * By mark the 'Ignore OVF update failure' the SD will deactivate even if the OVF update failed.
Tested with the following code: -------------------------------- ovirt-engine-4.2.1-0.2.el7.noarch vdsm-4.20.11-18.git92c490c.el7.centos.x86_64 The steps to reproduce are: 1) Create a new SD (NFS preferred) with a VM and disk base on it. 2) To make sure OVF update will be triggered, change the VM name. 3) On the 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. Expected result: The OVf update should fail and cause the deactivation to failed. Moving to VERIFIED
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017. Since the problem described in this bug report should be resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.