Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1136809

Summary: [ImportDomain]import storage domain fails on logs,"Could not get populated disk"
Product: [Retired] oVirt Reporter: Ori Gofen <ogofen>
Component: ovirt-engine-coreAssignee: Maor <mlipchuk>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.5CC: acanan, acathrow, amureini, ecohen, gklein, iheim, yeylon
Target Milestone: ---   
Target Release: 3.5.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-03 12:06:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1193195    
Attachments:
Description Flags
vdsm+engine logs none

Description Ori Gofen 2014-09-03 11:12:10 UTC
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:

Comment 1 Ori Gofen 2014-09-03 11:12:42 UTC
Created attachment 934045 [details]
vdsm+engine logs

Comment 2 Ori Gofen 2014-09-03 12:06:44 UTC
bugzilla bug! duplicate of BZ #1136808

*** This bug has been marked as a duplicate of bug 1136808 ***