[Ovirt-devel] Re: Issue with ISO provisioning
Perry Myers
pmyers at redhat.com
Wed Oct 15 13:24:59 UTC 2008
Darryl Pierce wrote:
> Perry Myers wrote:
>> I tried to provision a second guest using the same ISO image off of the
>> same NFS share. This failed with the following error in taskomatic:
>>> libvir: Storage error : no storage vol with matching name
>>> start_vm
>>> Task action processing failed: Libvirt::RetrieveError: Call to
>>> function virStorageVolLookupByName failed
>>> /usr/share/ovirt-server/task-omatic/./utils.rb:124:in
>>> `lookup_volume_by_name'
>>> /usr/share/ovirt-server/task-omatic/./utils.rb:124:in
>>> `connect_storage_pools'
>>> /usr/share/ovirt-server/task-omatic/./utils.rb:81:in `each'
>>> /usr/share/ovirt-server/task-omatic/./utils.rb:81:in
>>> `connect_storage_pools'
>>> /usr/share/ovirt-server/task-omatic/./task_vm.rb:314:in `start_vm'
>>> /usr/share/ovirt-server/task-omatic/taskomatic.rb:99
>>> /usr/share/ovirt-server/task-omatic/taskomatic.rb:88:in `each'
>>> /usr/share/ovirt-server/task-omatic/taskomatic.rb:88
>>> /usr/share/ovirt-server/task-omatic/taskomatic.rb:68:in `loop'
>>> /usr/share/ovirt-server/task-omatic/taskomatic.rb:68
>> Seems that if the NFS share is previously mounted as a storage pool in
>> libvirt, it causes taskomatic to fail. If I manually destroy the
>> storage pool for the NFS mount on the host and undefine it and then try
>> again, the start_vm succeeds and recreates the storage pool.
>>
>> This needs to be fixed...
>
> You shouldn't have to create a storage pool at all to provision an ISO
> from Cobbler. As long as the ISO image is on an NFS exported file system
> the Image record was given the hostname and export path, a storage pool
> need never be defined for it in oVirt.
*I* didn't create a storage pool. Your code did that in Taskomatic. What
I'm saying is if you create a vm that uses a cobbler image as provisioning
source, your code in taskomatic creates the storage pool on the node so
that you can access the iso.
If you try to provision another guest on the same node it fails, probably
because that storage pool already exists but is not tracked in the
database like other storage pools.
Perry
More information about the ovirt-devel
mailing list