Re: [ovirt-users] Failed to create live snapshot

2015-11-23 Thread Arman Khalatyan
What kind of storage are you using??
I had similar trouble with iscsi storage.
The workaround was to delete some bad symlinks in /rvem/data-center
The following steps are used to fix missing devices on the hosts:
Host->maintenance
On host rm -rf /rvem/data-center
yum reinstall vdsm
It will generate folder structure in /rvem
Before this backup your data. Maybe you hit another bug.
Good luck,
Arman
Hello,

I'm getting the following error when I try to create a snapshot of one VM.
Snapshots of all other VMs work as expected. I'm using oVirt 3.5 on Centos
7.

>Failed to create live snapshot 'fsbu3' for VM 'Odoo'. VM restart is
recommended. Note that using the created snapshot might cause data
inconsistency.

I think this is the relevant part of vdsm.log, what strikes me as odd is
the line:
>Thread-1192052::ERROR::2015-11-23
17:18:20,532::vm::4355::vm.Vm::(snapshot)
vmId=`581cebb3-7729-4c29-b98c-f9e04aa2fdd0`::The base volume doesn't exist:
{'device': 'disk', 'domainID': 'b4e7425a-53c7-40d4-befc-ea36ed7891fc',
'volumeID': '9a7fc7e0-60fc-4f67-9f97-2de4bc08f0a7', 'imageID':
'dfa1d0bf-a1f6-45bb-9574-ab020c0e8c9d'}
The part "The base volume doesn't exist" seems interesting.

Also interesting is that it does create a snapshot, though I don't know if
that snapshot is missing data.

Thread-1192048::DEBUG::2015-11-23
17:18:20,421::taskManager::103::Storage.TaskManager::(getTaskStatus) Entry.
taskID: 21a1c403-f306-40b1-bad8-377d0265ebca
Thread-1192048::DEBUG::2015-11-23
17:18:20,421::taskManager::106::Storage.TaskManager::(getTaskStatus)
Return. Response: {'code': 0, 'message': '1 jobs completed successfully',
'taskState': 'finished', 'taskResult': 'success', 'taskID':
'21a1c403-f306-40b1-bad8-377d0265ebca'}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::taskManager::123::Storage.TaskManager::(getAllTasksStatuses)
Return: {'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1
jobs completed successfully', 'taskState': 'finished', 'taskResult':
'success', 'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}
Thread-1192048::INFO::2015-11-23
17:18:20,422::logUtils::47::dispatcher::(wrapper) Run and protect:
getAllTasksStatuses, Return response: {'allTasksStatus':
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult': 'success',
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::task::1191::Storage.TaskManager.Task::(prepare)
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::finished: {'allTasksStatus':
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult': 'success',
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::task::595::Storage.TaskManager.Task::(_updateState)
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::moving from state preparing ->
state finished
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::resourceManager::940::Storage.ResourceManager.Owner::(releaseAll)
Owner.releaseAll requests {} resources {}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::resourceManager::977::Storage.ResourceManager.Owner::(cancelAll)
Owner.cancelAll requests {}
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::task::993::Storage.TaskManager.Task::(_decref)
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::ref 0 aborting False
Thread-1192048::DEBUG::2015-11-23
17:18:20,422::__init__::500::jsonrpc.JsonRpcServer::(_serveRequest) Return
'Host.getAllTasksStatuses' in bridge with
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs
completed successfully', 'taskState': 'finished', 'taskResult': 'success',
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}
Thread-1192048::DEBUG::2015-11-23
17:18:20,423::stompReactor::163::yajsonrpc.StompServer::(send) Sending
response
JsonRpc (StompReactor)::DEBUG::2015-11-23
17:18:20,423::stompReactor::98::Broker.StompAdapter::(handle_frame)
Handling message 
JsonRpcServer::DEBUG::2015-11-23
17:18:20,424::__init__::506::jsonrpc.JsonRpcServer::(serve_requests)
Waiting for request
Thread-1192049::DEBUG::2015-11-23
17:18:20,426::stompReactor::163::yajsonrpc.StompServer::(send) Sending
response
JsonRpc (StompReactor)::DEBUG::2015-11-23
17:18:20,438::stompReactor::98::Broker.StompAdapter::(handle_frame)
Handling message 
JsonRpcServer::DEBUG::2015-11-23
17:18:20,439::__init__::506::jsonrpc.JsonRpcServer::(serve_requests)
Waiting for request
Thread-1192050::DEBUG::2015-11-23
17:18:20,441::stompReactor::163::yajsonrpc.StompServer::(send) Sending
response
JsonRpc (StompReactor)::DEBUG::2015-11-23
17:18:20,442::stompReactor::98::Broker.StompAdapter::(handle_frame)
Handling message 
JsonRpcServer::DEBUG::2015-11-23
17:18:20,443::__init__::506::jsonrpc.JsonRpcServer::(serve_requests)
Waiting for request
Thread-1192051::DEBUG::2015-11-23
17:18:20,445::stompReactor::163::yajsonrpc.StompServer::(send) Sending
response
JsonRpc 

[ovirt-users] Failed to create live snapshot

2015-11-23 Thread mots
Hello,

I'm getting the following error when I try to create a snapshot of one VM. 
Snapshots of all other VMs work as expected. I'm using oVirt 3.5 on Centos 7.

>Failed to create live snapshot 'fsbu3' for VM 'Odoo'. VM restart is 
>recommended. Note that using the created snapshot might cause data 
>inconsistency.

I think this is the relevant part of vdsm.log, what strikes me as odd is the 
line:
>Thread-1192052::ERROR::2015-11-23 17:18:20,532::vm::4355::vm.Vm::(snapshot) 
>vmId=`581cebb3-7729-4c29-b98c-f9e04aa2fdd0`::The base volume doesn't exist: 
>{'device': 'disk', 'domainID': 'b4e7425a-53c7-40d4-befc-ea36ed7891fc', 
>'volumeID': '9a7fc7e0-60fc-4f67-9f97-2de4bc08f0a7', 'imageID': 
>'dfa1d0bf-a1f6-45bb-9574-ab020c0e8c9d'}
The part "The base volume doesn't exist" seems interesting.

Also interesting is that it does create a snapshot, though I don't know if that 
snapshot is missing data.

Thread-1192048::DEBUG::2015-11-23 
17:18:20,421::taskManager::103::Storage.TaskManager::(getTaskStatus) Entry. 
taskID: 21a1c403-f306-40b1-bad8-377d0265ebca
Thread-1192048::DEBUG::2015-11-23 
17:18:20,421::taskManager::106::Storage.TaskManager::(getTaskStatus) Return. 
Response: {'code': 0, 'message': '1 jobs completed successfully', 'taskState': 
'finished', 'taskResult': 'success', 'taskID': 
'21a1c403-f306-40b1-bad8-377d0265ebca'}
Thread-1192048::DEBUG::2015-11-23 
17:18:20,422::taskManager::123::Storage.TaskManager::(getAllTasksStatuses) 
Return: {'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs 
completed successfully', 'taskState': 'finished', 'taskResult': 'success', 
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}
Thread-1192048::INFO::2015-11-23 
17:18:20,422::logUtils::47::dispatcher::(wrapper) Run and protect: 
getAllTasksStatuses, Return response: {'allTasksStatus': 
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs 
completed successfully', 'taskState': 'finished', 'taskResult': 'success', 
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}}
Thread-1192048::DEBUG::2015-11-23 
17:18:20,422::task::1191::Storage.TaskManager.Task::(prepare) 
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::finished: {'allTasksStatus': 
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs 
completed successfully', 'taskState': 'finished', 'taskResult': 'success', 
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}}
Thread-1192048::DEBUG::2015-11-23 
17:18:20,422::task::595::Storage.TaskManager.Task::(_updateState) 
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::moving from state preparing -> 
state finished
Thread-1192048::DEBUG::2015-11-23 
17:18:20,422::resourceManager::940::Storage.ResourceManager.Owner::(releaseAll) 
Owner.releaseAll requests {} resources {}
Thread-1192048::DEBUG::2015-11-23 
17:18:20,422::resourceManager::977::Storage.ResourceManager.Owner::(cancelAll) 
Owner.cancelAll requests {}
Thread-1192048::DEBUG::2015-11-23 
17:18:20,422::task::993::Storage.TaskManager.Task::(_decref) 
Task=`ce3d857c-45d3-4acc-95a5-79484e457fc6`::ref 0 aborting False
Thread-1192048::DEBUG::2015-11-23 
17:18:20,422::__init__::500::jsonrpc.JsonRpcServer::(_serveRequest) Return 
'Host.getAllTasksStatuses' in bridge with 
{'21a1c403-f306-40b1-bad8-377d0265ebca': {'code': 0, 'message': '1 jobs 
completed successfully', 'taskState': 'finished', 'taskResult': 'success', 
'taskID': '21a1c403-f306-40b1-bad8-377d0265ebca'}}
Thread-1192048::DEBUG::2015-11-23 
17:18:20,423::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23 
17:18:20,423::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling 
message 
JsonRpcServer::DEBUG::2015-11-23 
17:18:20,424::__init__::506::jsonrpc.JsonRpcServer::(serve_requests) Waiting 
for request
Thread-1192049::DEBUG::2015-11-23 
17:18:20,426::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23 
17:18:20,438::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling 
message 
JsonRpcServer::DEBUG::2015-11-23 
17:18:20,439::__init__::506::jsonrpc.JsonRpcServer::(serve_requests) Waiting 
for request
Thread-1192050::DEBUG::2015-11-23 
17:18:20,441::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23 
17:18:20,442::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling 
message 
JsonRpcServer::DEBUG::2015-11-23 
17:18:20,443::__init__::506::jsonrpc.JsonRpcServer::(serve_requests) Waiting 
for request
Thread-1192051::DEBUG::2015-11-23 
17:18:20,445::stompReactor::163::yajsonrpc.StompServer::(send) Sending response
JsonRpc (StompReactor)::DEBUG::2015-11-23 
17:18:20,529::stompReactor::98::Broker.StompAdapter::(handle_frame) Handling 
message 
Thread-1192052::DEBUG::2015-11-23 
17:18:20,530::__init__::469::jsonrpc.JsonRpcServer::(_serveRequest) Calling 
'VM.snapshot' in bridge with {'vmID': '581cebb3-7729-4c29-b98c-f9e04aa2fdd0', 
'snapDrives': [{'baseVolumeID':