Bug 1247052 - Can't move disk to second iSCSI domain
Summary: Can't move disk to second iSCSI domain
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: General
Version: 3.5.3.1
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ovirt-3.6.0-rc
: 3.6.0
Assignee: Maor
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-27 08:49 UTC by Tiemen Ruiten
Modified: 2017-01-09 16:37 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-10-07 12:43:25 UTC
oVirt Team: Storage
Embargoed:
ylavi: ovirt-3.6.0?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)
vdsm log (54.46 KB, application/x-gzip)
2015-07-27 08:49 UTC, Tiemen Ruiten
no flags Details
engine log (232.60 KB, application/x-gzip)
2015-07-27 08:50 UTC, Tiemen Ruiten
no flags Details

Description Tiemen Ruiten 2015-07-27 08:49:35 UTC
Created attachment 1056520 [details]
vdsm log

Description of problem:

Can't move disk to second iSCSI domain


Version-Release number of selected component (if applicable):

3.5.3.1


How reproducible:

Steps to Reproduce:
1. Create a 2nd iSCSI domain
2. Attempt to move a disk to it
3. Move fails with error message "User $user@$domain have [sic] failed to move disk $diskname to domain $domainname."

Actual results:

Disk fails to move

Expected results:

The disk is moved to the 2nd iSCSI domain


Additional info:

Errors in the log files can be found at around 11:35

Comment 1 Tiemen Ruiten 2015-07-27 08:50:34 UTC
Created attachment 1056521 [details]
engine log

Comment 2 Allon Mureinik 2015-07-28 07:55:30 UTC
The underlying issue seems to be the following:

e43ea67a-dc3d-484a-9140-9ec9a53ea6e4::WARNING::2015-07-22 12:06:11,797::resourceManager::591::Storage.ResourceManager::(registerResource) Resource factory failed to create resource '05f75b87-e6c6-46c2-8e2d-b0bd7b3a8cd4_imageNS.595b1faa-82d0-4133-9618-30a5900240d5'. Canceling request.
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/resourceManager.py", line 587, in registerResource
    obj = namespaceObj.factory.createResource(name, lockType)
  File "/usr/share/vdsm/storage/resourceFactories.py", line 193, in createResource
    lockType)
  File "/usr/share/vdsm/storage/resourceFactories.py", line 122, in __getResourceCandidatesList
    imgUUID=resourceName)
  File "/usr/share/vdsm/storage/image.py", line 185, in getChain
    srcVol = volclass(self.repoPath, sdUUID, imgUUID, uuidlist[0])
  File "/usr/share/vdsm/storage/blockVolume.py", line 80, in __init__
    volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
  File "/usr/share/vdsm/storage/volume.py", line 144, in __init__
    self.validate()
  File "/usr/share/vdsm/storage/blockVolume.py", line 89, in validate
    volume.Volume.validate(self)
  File "/usr/share/vdsm/storage/volume.py", line 156, in validate
    self.validateImagePath()
  File "/usr/share/vdsm/storage/blockVolume.py", line 430, in validateImagePath
    raise se.ImagePathError(imageDir)
ImagePathError: Image path does not exist or cannot be accessed/created: (u'/rhev/data-center/cd8bd3ca-4133-4f5d-9139-4d2c354abaf5/05f75b87-e6c6-46c2-8e2d-b0bd7b3a8cd4/images/595b1faa-82d0-4133-9618-30a5900240d5',)


Maor, as this weeks community contact, please take a look.
Thanks!

Comment 3 Maor 2015-07-28 09:38:50 UTC
Seems to work on my environment.

From the logs I can see that the file is already exists in the Storage:

OSError: [Errno 17] File exists: '/rhev/data-center/cd8bd3ca-4133-4f5d-9139-4d2c354abaf5/05f75b87-e6c6-46c2-8e2d-b0bd7b3a8cd4/images/595b1faa-82d0-4133-9618-30a5900240d5'

Do you have any specific reproduce steps? does it happens with all the images on the Storage Domain?

Comment 4 Maor 2015-10-07 12:43:25 UTC
Closing this since there was no response from the user, and it seems to work on my env.
Please feel free to re-open once new information will be provided.


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