Created attachment 1060321 [details] logs Description of problem: If you try to make live snap with enabled IO Threads, the operation will fail. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Create a vm from template 2. On resource allocation tab enable the IO Threads 3. Start vm 4. Create snap Actual results: Failed to create live snapshot '2' for VM 'enaxtest7'. VM restart is recommended. Note that using the created snapshot might cause data inconsistency. Expected results: Snapshot '2' creation for VM 'enaxtest7' has been completed. Additional info: If need more information, just write me.
enax - the failure is seen in the engine log circa 2015-08-07 05:05, but the VDSM log only starts on 2015-08-07 09:05, and I cannot see the error there. Could you please upload the VDSM that contains the error?
Michal - I'm not quite sure if this is in Storage or Virt's domain. Taking to Storage for initial investigation, but your guys should probably be in the loop too.
Created attachment 1060983 [details] logs2
Ahh sorry, wrong timezone settings on node.
(In reply to Allon Mureinik from comment #2) > Michal - I'm not quite sure if this is in Storage or Virt's domain. Taking > to Storage for initial investigation, but your guys should probably be in > the loop too. I only see Thread-123613::ERROR::2015-08-10 11:00:42,668::vm::3024::virt.vm::(snapshot) vmId=`97018914-a0e7-43b6-a4e1-73ee2d88007f`::The base volume doesn't exist: {'device': 'disk', 'domainID': u'bda691fe-f8c4-42cd-9 727-cb709d72b2f5', 'volumeID': u'db09bb38-331d-49aa-96e6-a7c9b9e6589f', 'imageID': u'28ca3b3f-ebc3-4643-ac81-58231421c032'} Not sure if iothreads are really the difference here
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
this is an automated message. oVirt 3.6.0 RC3 has been released and GA is targeted to next week, Nov 4th 2015. Please review this bug and if not a blocker, please postpone to a later release. All bugs not postponed on GA release will be automatically re-targeted to - 3.6.1 if severity >= high - 4.0 if severity < high
Hi enax, I could not reproduce this issue on latest 3.6. Are there some additional steps other than the ones mentioned ? Is the problem still happening to you ? Thanks
This bug is not marked for z-stream, yet the milestone is for a z-stream version, therefore the milestone has been reset. Please set the correct milestone or add the z-stream flag.
Please reopen this issue with the needed info. We require the info to resolve the issue. Thanks!