Bug 1640225 - Failed to migrate VM disk: unsupported configuration: nothing selected for snapshot
Summary: Failed to migrate VM disk: unsupported configuration: nothing selected for sn...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.2.6.2
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ovirt-4.2.8
: ---
Assignee: Eyal Shenitzky
QA Contact: Elad
URL:
Whiteboard:
Depends On:
Blocks: 1654891
TreeView+ depends on / blocked
 
Reported: 2018-10-17 15:09 UTC by Evelina Shames
Modified: 2019-01-22 10:23 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-01-22 10:23:08 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.2+
rule-engine: ovirt-4.3+
rule-engine: blocker+


Attachments (Terms of Use)
logs (2.50 MB, application/zip)
2018-10-17 15:09 UTC, Evelina Shames
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1654891 0 urgent CLOSED Engine sent duplicate SnapshotVDSCommand, causing data corruption 2022-03-13 17:03:37 UTC
oVirt gerrit 96139 0 master MERGED core: persist CreateSnapshotForVmCommand#performNextOperation 2018-12-12 10:25:56 UTC
oVirt gerrit 96165 0 ovirt-engine-4.2 MERGED core: persist CreateSnapshotForVmCommand#performNextOperation 2018-12-13 08:29:33 UTC

Internal Links: 1654891 1658589

Description Evelina Shames 2018-10-17 15:09:12 UTC
Created attachment 1494893 [details]
logs

Description of problem:
Failed to migrate VM disk after snapshot creation failure with the following errors:

Engine:
2018-09-20 03:35:37,731+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-57) [disks_syncAction_f36f5e3b-ce04-40a2] Failed in 'SnapshotVDS' method
2018-09-20 03:35:37,764+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-57) [disks_syncAction_f36f5e3b-ce04-40a2] EVENT_ID: VDS_BROKER_COMMAND_FAILURE(10,802), VDSM host_mixed_3 command SnapshotVDS failed: Snapshot failed
2018-09-20 03:35:37,764+03 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.SnapshotVDSCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-57) [disks_syncAction_f36f5e3b-ce04-40a2] Command 'SnapshotVDSCommand(HostName = host_mixed_3, SnapshotVDSCommandParameters:{hostId='62de5a0b-f8ff-43b0-bae5-75c8efe6185d', vmId='5efecd8e-ad0b-4ecd-b539-cc505eee1391'})' execution failed: VDSGenericException: VDSErrorException: Failed to SnapshotVDS, error = Snapshot failed, code = 48
2018-09-20 03:35:42,831+03 ERROR [org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand] (EE-ManagedThreadFactory-engineScheduled-Thread-49) [disks_syncAction_f36f5e3b-ce04-40a2] Ending command 'org.ovirt.engine.core.bll.storage.lsm.LiveMigrateDiskCommand' with failure.
2018-09-20 03:35:43,120+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engineScheduled-Thread-49) [disks_syncAction_f36f5e3b-ce04-40a2] EVENT_ID: USER_MOVED_DISK_FINISHED_FAILURE(2,011), User admin@internal-authz have failed to move disk disk_virtio_scsiraw_2003292029 to domain nfs_0.

VDSM:
2018-09-20 03:35:37,727+0300 ERROR (jsonrpc/3) [virt.vm] (vmId='5efecd8e-ad0b-4ecd-b539-cc505eee1391') Unable to take snapshot (vm:4620)
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdsm/virt/vm.py", line 4617, in snapshot
    self._dom.snapshotCreateXML(snapxml, snapFlags)
  File "/usr/lib/python2.7/site-packages/vdsm/virt/virdomain.py", line 98, in f
    ret = attr(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/libvirtconnection.py", line 130, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/common/function.py", line 92, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2618, in snapshotCreateXML
    if ret is None:raise libvirtError('virDomainSnapshotCreateXML() failed', dom=self)
libvirtError: unsupported configuration: nothing selected for snapshot


Version-Release number of selected component (if applicable):
ovirt-engine-4.2.7-0.1.el7ev.noarch
vdsm-4.20.40-1.el7ev.x86_64


How reproducible:
Once

Steps to Reproduce:
1. Create a VM with 5 disks from all the disks permutations
2. Run the VM
3. Start dd operation to all the disks
4. Move all the VM disks concurrently to different storage domain

Actual results:
Failed to migrate VM disk

Expected results:
Operation should succeed. 

Additional info:
logs are attached

Comment 1 Benny Zlotnik 2018-10-22 09:00:53 UTC
What is the libvirt version?
Do we have the libvirtd logs?

Comment 2 Evelina Shames 2018-11-11 11:29:05 UTC
(In reply to Benny Zlotnik from comment #1)
> What is the libvirt version? libvirt-4.5.0-9.el7.x86_64
> Do we have the libvirtd logs? No, there were no libvirt logs

Comment 3 Eyal Shenitzky 2018-12-10 09:30:57 UTC
(In reply to Evelina Shames from comment #2)
> (In reply to Benny Zlotnik from comment #1)
> > What is the libvirt version? libvirt-4.5.0-9.el7.x86_64
> > Do we have the libvirtd logs? No, there were no libvirt logs

Evelina, Can you please respond to Benny's comment.

Moreover, did you managed to reproduce it more than once?

Comment 4 Elad 2018-12-10 14:15:59 UTC
Tal, this should be the U/S bug of bug 1640225. Please re-target to 4.2.8

Comment 5 Tal Nisan 2018-12-10 15:05:42 UTC
(In reply to Elad from comment #4)
> Tal, this should be the U/S bug of bug 1640225. Please re-target to 4.2.8

You meant bug 1654891, doesn't really matter as the D/S bug will cover both after the clone to zstream but OK, I'll change.

Comment 6 Elad 2019-01-16 13:50:47 UTC
Moving to VERIFIED based on latest 4.2.8 regression cycles results.
Also executed few times the test case (TestCase21907) that this bug was originally discovered by.
The issue wasn't seen again.

Used:
vdsm-4.20.46-1.el7ev.x86_64
ovirt-engine-4.2.8.2-0.1.el7

Comment 7 Sandro Bonazzola 2019-01-22 10:23:08 UTC
This bugzilla is included in oVirt 4.2.8 release, published on January 22nd 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.2.8 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.


Note You need to log in before you can comment on or make changes to this bug.