Bug 769871 - [ovirt] [vdsm] Don't try to schedule SPM tasks on HSM
Summary: [ovirt] [vdsm] Don't try to schedule SPM tasks on HSM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.3.4
Assignee: Dan Kenigsberg
QA Contact:
URL:
Whiteboard: storage
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-22 15:36 UTC by Haim
Modified: 2016-02-10 16:51 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-12 09:36:27 UTC
oVirt Team: Storage


Attachments (Terms of Use)

Description Haim 2011-12-22 15:36:04 UTC
Description of problem:

during live snapshot testing, i'v hit a case where i managed somehow to run createVolume from hsm host, and got the following: 

Thread-671::ERROR::2011-12-21 13:07:48,128::task::855::TaskManager.Task::(_setError) Task=`12292bf9-1578-4acd-a814-7c799392dff1`::Unexpected error
 Traceback (most recent call last):
   File "/usr/share/vdsm/storage/task.py", line 863, in _run
     return fn(*args, **kargs)
   File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
     res = f(*args, **kwargs)
   File "/usr/share/vdsm/storage/hsm.py", line 1097, in public_createVolume
     srcImgUUID, srcVolUUID
   File "/usr/share/vdsm/storage/hsm.py", line 544, in _spmSchedule
     self.taskMng.scheduleJob("spm", pool.tasksDir, vars.task, name, func, *args)
 AttributeError: 'setMaxHostID' object has no attribute 'tasksDir'

createVolume should only be executed on SPM machine, the actual error here is wrong, and command should be blocked before it reaches that point. 

git commit: 67800f45d6c776a9964327429ff6ddc8feea353a

repro:

execute create volume task on HSM using vdsClient.

Comment 1 Itamar Heim 2013-03-12 09:36:27 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.


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