Created attachment 1231450 [details] engine & vdsm logs from both hosts Description of problem: With a VM without disks , OVF file is not created after Force updateOVF on a storage domain Version-Release number of selected component (if applicable): 4.1.0-0.2.master.20161212172238.gitea103bd.el7.centos How reproducible: 100% Steps to Reproduce: Setup : 1 DC 1 cluster (C1) 2 Hosts in cluster C1 ( host1 - SPM , host2 - HSM ) 3 storage domains (NFS , gluster , iscsi) 1. Can be reproduced creating ONLY 1 SD ( SD type does not matter) & 1 host . 2. Scedualed updateOVF initiated to avoid bug 1403581 ( last update was 2016-12-14 07:46:23) 3. create a VM1 without disks . 4. force updateOVF on the NFS storage domain (Dec 14 08:33:22 IST 2016) Actual results: OVF store of the NFS domain seems to be updated by engine & VDSM logs BUT No OVF file created . Expected results: OVF store of the NFS doamin should be updated & ovf file created with the VM description . Additional info: I saw only the info.json file , No OVF file : [root@camel-vdsb test1]# dd if=/rhev/data-center/4665c59b-2b27-4643-9b12-150fb88323d5/9e62e086-69b9-4ac8-8368-078d60489538/images/63d057c6-4e19-42ac-b6b0-298e32588478/a5d300d5-6dca-4134-8c93-59debb405d57 of=/mnt/test1/ovfstore 20+0 records in 20+0 records out 10240 bytes (10 kB) copied, 0.000230757 s, 44.4 MB/s [root@camel-vdsb test1]# tar -xvf ovfstore info.json [root@camel-vdsb test1]# cat info.json { "Last Updated" : "Wed Dec 14 08:33:22 IST 2016", "Storage Domains" : [ { "uuid" : "9e62e086-69b9-4ac8-8368-078d60489538" } ]
More info : After scheduled updateOVF store OVF file is indeed created so it looks like its a clear FORCE updateOVF issue.
If it's only happening for a VM without disks, I'm OK with closing this bug as WONTFIX.
(In reply to Yaniv Kaul from comment #2) > If it's only happening for a VM without disks, I'm OK with closing this bug > as WONTFIX. This bug is one scenario of many scenarios that force updateOVF does not work in. I aggregated all the issues in bug #1404607 so you can dup this bug to bug #1404607 . Summery of what is working/not working (taken from bug #1404607 ): Not Working (meaning OVF store content is NOT updated) : 1)If not scheduled update Nothing works ! - bug 1403581 2) After scheduled update , modify VM/disk + force update: - create VM No disk - bug #1404565 - create VM +disk (or 2disks) - bug - delete disk from VM
*** This bug has been marked as a duplicate of bug 1404607 ***