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@us.ibm.com
From: agl@linux.vnet.ibm.com To: VDSM Project Development vdsm-devel@lists.fedorahosted.org Date: 09/02/2011 10:31 AM Subject: Re: createVolume in recovered state Sent by: vdsm-devel-bounces@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@us.ibm.com IBM Linux Technology Center _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/vdsm-devel