Created attachment 934044[details]
vdsm+engine logs
Description of problem:
The operation of importing a populated storage domain to a new setup,fails every time on logs:
2014-09-03 13:08:59,953 ERROR [org.ovirt.engine.core.bll.GetUnregisteredDisksQuery] (ajp--127.0.0.1-8702-2) [3cf8853c] Could not get populated disk, reason: null
2014-09-03 13:08:59,962 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetVolumesListVDSCommand] (ajp--127.0.0.1-8702-2) [3cf8853c] START, GetVolumesListVDSCommand( storagePoolId = 00000002-0002-0002-0002-000000000389, ignoreFailoverLimit = false, storageDomainId = ffca62e7-397c-4533-9df3-446cc6580ee6, imageGroupId = 989efd20-f30d-44ae-9237-b627a1a86a6e), log id: 523f6582
the operation itself is successful
Version-Release number of selected component (if applicable):
rc1.1
How reproducible:
100%
Steps to Reproduce:
1.import a populated domain to a new setup(not as master domain)
Actual results:
the operation fails on logs
Expected results:
there is no use for confusing ERRORs if the operation is successful,otherwise, if there's a problem with the import flow,it should be fixed
Additional info:
I'm not sure I understand the description of this bug - is it about redundant ERRORs in the log for a successful operation, or does the operation just FAIL?
Allon,option 1.
False Errors can be very confusing,we shouldn't allow it in a sensitive operation like recovering a domain.
(In reply to Allon Mureinik from comment #2)
> I'm not sure I understand the description of this bug - is it about
> redundant ERRORs in the log for a successful operation, or does the
> operation just FAIL?
(In reply to Ori from comment #3)
> Allon,option 1.
> False Errors can be very confusing,we shouldn't allow it in a sensitive
> operation like recovering a domain.
Agreed, completely.
Just needed to understand what exactly the problem is before we can fix it :-)
The origin of the ERROR is that we try to register a disk with snapshots:
GetVolumesList for image 558be124-aad0-4da8-950c-339a7892319d
returns two volumes: [a49a902c-1edf-489c-8edd-0fce8be07bde, 370d21cd-aeed-4063-930b-3c36fc8b0ee6]
That is why the registration fails.
The fix is on the way
Created attachment 934044 [details] vdsm+engine logs Description of problem: The operation of importing a populated storage domain to a new setup,fails every time on logs: 2014-09-03 13:08:59,953 ERROR [org.ovirt.engine.core.bll.GetUnregisteredDisksQuery] (ajp--127.0.0.1-8702-2) [3cf8853c] Could not get populated disk, reason: null 2014-09-03 13:08:59,962 INFO [org.ovirt.engine.core.vdsbroker.irsbroker.GetVolumesListVDSCommand] (ajp--127.0.0.1-8702-2) [3cf8853c] START, GetVolumesListVDSCommand( storagePoolId = 00000002-0002-0002-0002-000000000389, ignoreFailoverLimit = false, storageDomainId = ffca62e7-397c-4533-9df3-446cc6580ee6, imageGroupId = 989efd20-f30d-44ae-9237-b627a1a86a6e), log id: 523f6582 the operation itself is successful Version-Release number of selected component (if applicable): rc1.1 How reproducible: 100% Steps to Reproduce: 1.import a populated domain to a new setup(not as master domain) Actual results: the operation fails on logs Expected results: there is no use for confusing ERRORs if the operation is successful,otherwise, if there's a problem with the import flow,it should be fixed Additional info: