8:12 a.m.
Hi,
I got VDSM to installed by building and installing the RPM. Thank you! I
am now trying out the CLI and trying to create a virtual machine. I was
able to create a storage domain, storage pool, and volume, but was
unsuccessful at creating the virtual machine.
I used the following code:
...
print "Creating volume..."
print s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB, COW_FORMAT,
SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
print "Creating VM..."
print s.create(dict(vmId=vmId, drives=[dict(poolID=spUUID,
domainID=sdUUID, imageID=imgUUID, volumeID=volUUID)],
...
I get the following output:
Creating volume...
{'status': {'message': 'OK', 'code': 0},
'uuid':
'e38311cd-b872-48dd-a426-d4c4668a0cb5'}
Creating VM...
{'status': {'message': 'Recovering from crash or Initializing',
'code': 99}}
I browsed through the task list and found that the task to create the
volume is in "recovered state":
# cat e38311cd-b872-48dd-a426-d4c4668a0cb5.task
persistPolicy = auto
nrecoveries = 0
recoveryPolicy = auto
tag = spm
njobs = 1
id = e38311cd-b872-48dd-a426-d4c4668a0cb5
name = createVolume
cleanPolicy = manual
metadataVersion = 1
priority = low
state = recovered
store
= /rhev/data-center/ce132359-6405-4ab3-8d2b-7d1a27a625f9/tasks
Is there a reason why creating the volume would crash and recover, but not
complete? The task seems to be just hanging around.
Thank you,
-------------------------------------
Thang Pham
IBM Poughkeepsie
9:13 a.m.
On Fri, Sep 02, 2011 at 09:12:55AM -0400, Thang Pham wrote:
Hi,
I got VDSM to installed by building and installing the RPM. Thank you! I
am now trying out the CLI and trying to create a virtual machine. I was
able to create a storage domain, storage pool, and volume, but was
unsuccessful at creating the virtual machine.
I used the following code:
...
print "Creating volume..."
print s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB, COW_FORMAT,
SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
print "Creating VM..."
print s.create(dict(vmId=vmId, drives=[dict(poolID=spUUID,
domainID=sdUUID, imageID=imgUUID, volumeID=volUUID)],
...
I get the following output:
Creating volume...
{'status': {'message': 'OK', 'code': 0},
'uuid':
'e38311cd-b872-48dd-a426-d4c4668a0cb5'}
Creating VM...
{'status': {'message': 'Recovering from crash or
Initializing',
'code': 99}}
I browsed through the task list and found that the task to create the
volume is in "recovered state":
# cat e38311cd-b872-48dd-a426-d4c4668a0cb5.task
persistPolicy = auto
nrecoveries = 0
recoveryPolicy = auto
tag = spm
njobs = 1
id = e38311cd-b872-48dd-a426-d4c4668a0cb5
name = createVolume
cleanPolicy = manual
metadataVersion = 1
priority = low
state = recovered
store
= /rhev/data-center/ce132359-6405-4ab3-8d2b-7d1a27a625f9/tasks
Is there a reason why creating the volume would crash and recover, but not
complete? The task seems to be just hanging around.
It's not immediately obvious to me why it is failing. I would recommend
checking the vdsm log: /var/log/vdsm/vdsm.log
--
Adam Litke <agl(a)us.ibm.com>
IBM Linux Technology Center
9:35 a.m.
----- Original Message -----
On Fri, Sep 02, 2011 at 09:12:55AM -0400, Thang Pham wrote:
>
> Hi,
>
> I got VDSM to installed by building and installing the RPM. Thank
> you! I
> am now trying out the CLI and trying to create a virtual machine. I
> was
> able to create a storage domain, storage pool, and volume, but was
> unsuccessful at creating the virtual machine.
>
> I used the following code:
> ...
> print "Creating volume..."
> print s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB, COW_FORMAT,
> SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
> print "Creating VM..."
> print s.create(dict(vmId=vmId, drives=[dict(poolID=spUUID,
> domainID=sdUUID, imageID=imgUUID, volumeID=volUUID)],
> ...
>
> I get the following output:
> Creating volume...
> {'status': {'message': 'OK', 'code': 0},
'uuid':
> 'e38311cd-b872-48dd-a426-d4c4668a0cb5'}
> Creating VM...
> {'status': {'message': 'Recovering from crash or
Initializing',
> 'code': 99}}
>
> I browsed through the task list and found that the task to create
> the
> volume is in "recovered state":
> # cat e38311cd-b872-48dd-a426-d4c4668a0cb5.task
> persistPolicy = auto
> nrecoveries = 0
> recoveryPolicy = auto
> tag = spm
> njobs = 1
> id = e38311cd-b872-48dd-a426-d4c4668a0cb5
> name = createVolume
> cleanPolicy = manual
> metadataVersion = 1
> priority = low
> state = recovered
> store
> =
> /rhev/data-center/ce132359-6405-4ab3-8d2b-7d1a27a625f9/tasks
>
> Is there a reason why creating the volume would crash and recover,
> but not
> complete? The task seems to be just hanging around.
It's not immediately obvious to me why it is failing. I would
recommend
checking the vdsm log: /var/log/vdsm/vdsm.log
post vdsm.log as well as spm-lock.log
recovery is basically rollback not roll forward.
The task will not "disappear" until you run clearTask, but as you can see from
the status it is finished (recovered).
--
Adam Litke <agl(a)us.ibm.com>
IBM Linux Technology Center
_______________________________________________
vdsm-devel mailing list
vdsm-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel
10:04 a.m.
I ran the script again, and looking at the vdsm.log, I found this error
during the volume creation:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::ERROR::2011-09-02
10:47:14,587::task::875::TaskManager.Task::(_setError)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 883, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 312, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/spm.py", line 128, in run
return self.func(*args, **kwargs)
File "/usr/share/vdsm/storage/spm.py", line 1009, in createVolume
srcImgUUID=srcImgUUID, srcVolUUID=srcVolUUID)
File "/usr/share/vdsm/storage/fileSD.py", line 180, in createVolume
volUUID, desc, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 122, in create
pvol = FileVolume(repoPath, sdUUID, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 45, in __init__
volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
File "/usr/share/vdsm/storage/volume.py", line 117, in __init__
raise se.InvalidParameterException("imgUUID", imgUUID)
InvalidParameterException: Invalid parameter: 'imgUUID=None'
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::894::TaskManager.Task::(_run)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Task._run:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548 () {} failed - stopping task
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1229::TaskManager.Task::(stop)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::stopping in state running
(force False)
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1000::TaskManager.Task::(_decref)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::ref 1 aborting True
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,591::task::925::TaskManager.Task::(_runJobs)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::aborting: Task is aborted:
"Invalid parameter: 'imgUUID=None'" - code 100
It appears that it does not like what I put into the imgUUID, which was
generated using the following code:
imgUUID = str(uuid.uuid4())
But the imgUUID was not set to "None", which was what it interpreted. Is
there some other parameter missing for createVolume?
sizeGiB = 20
imgUUID = str(uuid.uuid4())
volUUID = str(uuid.uuid4())
s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB, COW_FORMAT,
SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
-------------------------------------
Thang Pham
IBM Poughkeepsie
Phone: (845) 433-7567
e-mail: thang.pham(a)us.ibm.com
From: agl(a)linux.vnet.ibm.com
To: VDSM Project Development <vdsm-devel(a)lists.fedorahosted.org>
Date: 09/02/2011 10:31 AM
Subject: Re: createVolume in recovered state
Sent by: vdsm-devel-bounces(a)lists.fedorahosted.org
On Fri, Sep 02, 2011 at 09:12:55AM -0400, Thang Pham wrote:
Hi,
I got VDSM to installed by building and installing the RPM. Thank you!
I
am now trying out the CLI and trying to create a virtual machine. I
was
able to create a storage domain, storage pool, and volume, but was
unsuccessful at creating the virtual machine.
I used the following code:
...
print "Creating volume..."
print s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB,
COW_FORMAT,
SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
print "Creating VM..."
print s.create(dict(vmId=vmId, drives=[dict(poolID=spUUID,
domainID=sdUUID, imageID=imgUUID, volumeID=volUUID)],
...
I get the following output:
Creating volume...
{'status': {'message': 'OK', 'code': 0},
'uuid':
'e38311cd-b872-48dd-a426-d4c4668a0cb5'}
Creating VM...
{'status': {'message': 'Recovering from crash or
Initializing',
'code': 99}}
I browsed through the task list and found that the task to create the
volume is in "recovered state":
# cat e38311cd-b872-48dd-a426-d4c4668a0cb5.task
persistPolicy = auto
nrecoveries = 0
recoveryPolicy = auto
tag = spm
njobs = 1
id = e38311cd-b872-48dd-a426-d4c4668a0cb5
name = createVolume
cleanPolicy = manual
metadataVersion = 1
priority = low
state = recovered
store
= /rhev/data-center/ce132359-6405-4ab3-8d2b-7d1a27a625f9/tasks
Is there a reason why creating the volume would crash and recover, but
not
complete? The task seems to be just hanging around.
It's not immediately obvious to me why it is failing. I would recommend
checking the vdsm log: /var/log/vdsm/vdsm.log
--
Adam Litke <agl(a)us.ibm.com>
IBM Linux Technology Center
_______________________________________________
vdsm-devel mailing list
vdsm-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel
6:21 a.m.
----- Original Message -----
I ran the script again, and looking at the vdsm.log, I found this
error
during the volume creation:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::ERROR::2011-09-02
10:47:14,587::task::875::TaskManager.Task::(_setError)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 883, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 312, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/spm.py", line 128, in run
return self.func(*args, **kwargs)
File "/usr/share/vdsm/storage/spm.py", line 1009, in createVolume
srcImgUUID=srcImgUUID, srcVolUUID=srcVolUUID)
File "/usr/share/vdsm/storage/fileSD.py", line 180, in createVolume
volUUID, desc, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 122, in create
pvol = FileVolume(repoPath, sdUUID, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 45, in __init__
volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
File "/usr/share/vdsm/storage/volume.py", line 117, in __init__
raise se.InvalidParameterException("imgUUID", imgUUID)
InvalidParameterException: Invalid parameter: 'imgUUID=None'
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::894::TaskManager.Task::(_run)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Task._run:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548 () {} failed - stopping task
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1229::TaskManager.Task::(stop)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::stopping in state running
(force False)
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1000::TaskManager.Task::(_decref)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::ref 1 aborting True
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,591::task::925::TaskManager.Task::(_runJobs)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::aborting: Task is
aborted:
"Invalid parameter: 'imgUUID=None'" - code 100
It appears that it does not like what I put into the imgUUID, which
was
generated using the following code:
imgUUID = str(uuid.uuid4())
But the imgUUID was not set to "None", which was what it interpreted.
Is
there some other parameter missing for createVolume?
Any storage verb you run gets logged with the parameters you passed (passwords are changed
into asterisks). If you attach the log we'll be able to help you more.
sizeGiB = 20
imgUUID = str(uuid.uuid4())
volUUID = str(uuid.uuid4())
s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB, COW_FORMAT,
SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
-------------------------------------
Thang Pham
IBM Poughkeepsie
Phone: (845) 433-7567
e-mail: thang.pham(a)us.ibm.com
From: agl(a)linux.vnet.ibm.com
To: VDSM Project Development <vdsm-devel(a)lists.fedorahosted.org>
Date: 09/02/2011 10:31 AM
Subject: Re: createVolume in recovered state
Sent by: vdsm-devel-bounces(a)lists.fedorahosted.org
On Fri, Sep 02, 2011 at 09:12:55AM -0400, Thang Pham wrote:
>
> Hi,
>
> I got VDSM to installed by building and installing the RPM. Thank
> you!
I
> am now trying out the CLI and trying to create a virtual machine. I
> was
> able to create a storage domain, storage pool, and volume, but was
> unsuccessful at creating the virtual machine.
>
> I used the following code:
> ...
> print "Creating volume..."
> print s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB,
COW_FORMAT,
> SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
> print "Creating VM..."
> print s.create(dict(vmId=vmId, drives=[dict(poolID=spUUID,
> domainID=sdUUID, imageID=imgUUID, volumeID=volUUID)],
> ...
>
> I get the following output:
> Creating volume...
> {'status': {'message': 'OK', 'code': 0},
'uuid':
> 'e38311cd-b872-48dd-a426-d4c4668a0cb5'}
> Creating VM...
> {'status': {'message': 'Recovering from crash or
Initializing',
> 'code': 99}}
>
> I browsed through the task list and found that the task to create
> the
> volume is in "recovered state":
> # cat e38311cd-b872-48dd-a426-d4c4668a0cb5.task
> persistPolicy = auto
> nrecoveries = 0
> recoveryPolicy = auto
> tag = spm
> njobs = 1
> id = e38311cd-b872-48dd-a426-d4c4668a0cb5
> name = createVolume
> cleanPolicy = manual
> metadataVersion = 1
> priority = low
> state = recovered
> store
> =
> /rhev/data-center/ce132359-6405-4ab3-8d2b-7d1a27a625f9/tasks
>
> Is there a reason why creating the volume would crash and recover,
> but
not
> complete? The task seems to be just hanging around.
It's not immediately obvious to me why it is failing. I would
recommend
checking the vdsm log: /var/log/vdsm/vdsm.log
--
Adam Litke <agl(a)us.ibm.com>
IBM Linux Technology Center
_______________________________________________
vdsm-devel mailing list
vdsm-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel
_______________________________________________
vdsm-devel mailing list
vdsm-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel
2:24 p.m.
On Fri, Sep 02, 2011 at 11:04:52AM -0400, Thang Pham wrote:
I ran the script again, and looking at the vdsm.log, I found this
error
during the volume creation:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::ERROR::2011-09-02
10:47:14,587::task::875::TaskManager.Task::(_setError)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 883, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 312, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/spm.py", line 128, in run
return self.func(*args, **kwargs)
File "/usr/share/vdsm/storage/spm.py", line 1009, in createVolume
srcImgUUID=srcImgUUID, srcVolUUID=srcVolUUID)
File "/usr/share/vdsm/storage/fileSD.py", line 180, in createVolume
volUUID, desc, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 122, in create
pvol = FileVolume(repoPath, sdUUID, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 45, in __init__
volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
File "/usr/share/vdsm/storage/volume.py", line 117, in __init__
raise se.InvalidParameterException("imgUUID", imgUUID)
InvalidParameterException: Invalid parameter: 'imgUUID=None'
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::894::TaskManager.Task::(_run)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Task._run:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548 () {} failed - stopping task
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1229::TaskManager.Task::(stop)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::stopping in state running
(force False)
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1000::TaskManager.Task::(_decref)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::ref 1 aborting True
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,591::task::925::TaskManager.Task::(_runJobs)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::aborting: Task is aborted:
"Invalid parameter: 'imgUUID=None'" - code 100
It appears that it does not like what I put into the imgUUID, which was
generated using the following code:
imgUUID = str(uuid.uuid4())
But the imgUUID was not set to "None", which was what it interpreted. Is
there some other parameter missing for createVolume?
sizeGiB = 20
imgUUID = str(uuid.uuid4())
volUUID = str(uuid.uuid4())
s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB, COW_FORMAT,
SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
Thang, have you resolved this issue by now? I believe it would be solved
if you pass two more args to createVolume, or apply the following patch
to Vdsm:
--- a/vdsm/storage/spm.py
+++ b/vdsm/storage/spm.py
@@ -1410,7 +1410,7 @@ class SPM:
self.log.warning("spm.uploadVolume: SP %s SD %s img %s Vol %s -
teardown failed")
- def public_createVolume(self, sdUUID, spUUID, imgUUID, size, volFormat, preallocate,
diskType, volUUID, desc, srcImgUUID=None, srcVolUUID=None):
+ def public_createVolume(self, sdUUID, spUUID, imgUUID, size, volFormat, preallocate,
diskType, volUUID, desc, srcImgUUID=volume.BLANK_UUID, srcVolUUID=volume.BLANK_UUID):
"""
Create a new volume
Function Type: SPM
Does this solve the problem for you?
Dan.
8:44 a.m.
Hi Dan,
I initially thought that the errors I got were because my code level was
out dated, so I updated it to the latest available. I no longer receive
that error, but something totally new now, which has something to do with
my configuration. I will be looking into it this week.
Thanks,
-------------------------------------
Thang Pham
IBM Poughkeepsie
From: Dan Kenigsberg <danken(a)redhat.com>
To: VDSM Project Development <vdsm-devel(a)lists.fedorahosted.org>
Date: 09/14/2011 03:25 PM
Subject: Re: createVolume in recovered state
Sent by: vdsm-devel-bounces(a)lists.fedorahosted.org
On Fri, Sep 02, 2011 at 11:04:52AM -0400, Thang Pham wrote:
I ran the script again, and looking at the vdsm.log, I found this
error
during the volume creation:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::ERROR::2011-09-02
10:47:14,587::task::875::TaskManager.Task::(_setError)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Unexpected error
Traceback (most recent call last):
File "/usr/share/vdsm/storage/task.py", line 883, in _run
return fn(*args, **kargs)
File "/usr/share/vdsm/storage/task.py", line 312, in run
return self.cmd(*self.argslist, **self.argsdict)
File "/usr/share/vdsm/storage/spm.py", line 128, in run
return self.func(*args, **kwargs)
File "/usr/share/vdsm/storage/spm.py", line 1009, in createVolume
srcImgUUID=srcImgUUID, srcVolUUID=srcVolUUID)
File "/usr/share/vdsm/storage/fileSD.py", line 180, in createVolume
volUUID, desc, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 122, in create
pvol = FileVolume(repoPath, sdUUID, srcImgUUID, srcVolUUID)
File "/usr/share/vdsm/storage/fileVolume.py", line 45, in __init__
volume.Volume.__init__(self, repoPath, sdUUID, imgUUID, volUUID)
File "/usr/share/vdsm/storage/volume.py", line 117, in __init__
raise se.InvalidParameterException("imgUUID", imgUUID)
InvalidParameterException: Invalid parameter: 'imgUUID=None'
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::894::TaskManager.Task::(_run)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::Task._run:
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548 () {} failed - stopping task
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1229::TaskManager.Task::(stop)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::stopping in state running
(force False)
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,590::task::1000::TaskManager.Task::(_decref)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::ref 1 aborting True
a71ad655-ec9e-4452-bcbf-8cfa9ff9a548::DEBUG::2011-09-02
10:47:14,591::task::925::TaskManager.Task::(_runJobs)
Task=`a71ad655-ec9e-4452-bcbf-8cfa9ff9a548`::aborting: Task is
aborted:
"Invalid parameter: 'imgUUID=None'" - code 100
It appears that it does not like what I put into the imgUUID, which was
generated using the following code:
imgUUID = str(uuid.uuid4())
But the imgUUID was not set to "None", which was what it interpreted. Is
there some other parameter missing for createVolume?
sizeGiB = 20
imgUUID = str(uuid.uuid4())
volUUID = str(uuid.uuid4())
s.createVolume(sdUUID, spUUID, imgUUID, sizeGiB, COW_FORMAT,
SPARSE_VOL, LEAF_VOL, volUUID, "My volume")
Thang, have you resolved this issue by now? I believe it would be solved
if you pass two more args to createVolume, or apply the following patch
to Vdsm:
--- a/vdsm/storage/spm.py
+++ b/vdsm/storage/spm.py
@@ -1410,7 +1410,7 @@ class SPM:
self.log.warning("spm.uploadVolume: SP %s SD %s img %s Vol
%s - teardown failed")
- def public_createVolume(self, sdUUID, spUUID, imgUUID, size,
volFormat, preallocate, diskType, volUUID, desc, srcImgUUID=None,
srcVolUUID=None):
+ def public_createVolume(self, sdUUID, spUUID, imgUUID, size,
volFormat, preallocate, diskType, volUUID, desc,
srcImgUUID=volume.BLANK_UUID, srcVolUUID=volume.BLANK_UUID):
"""
Create a new volume
Function Type: SPM
Does this solve the problem for you?
Dan.
_______________________________________________
vdsm-devel mailing list
vdsm-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/vdsm-devel
4617
days inactive
4630
days old
vdsm-devel@lists.fedorahosted.org
6 comments
4 participants
participants (4)
-
abaron＠redhat.com -
agl＠us.ibm.com -
Dan Kenigsberg -
Thang Pham