Ovirt devel - Jan 2009 - iSCSI LVM Issues (State remains pending_setup)

Hi Guys,

Having a bit of an issue with oVirt and it's Logical Voluming of an iSCSI
target.

Problem Overview:

Upon creating an adding an iSCSI target to the oVirt management interface and
having it initialised, clicking the 'Add new volume' feature creates a
logical volume in the interface with a status of 'pending_setup'.

Reproduction:

On the physical hardware:
[root at physical ~]# lvcreate -n iSCSI3 -L +15G /dev/VolGroup00
[root at physical ~]# tgtadm --lld iscsi --op new --mode target --tid 3 -T
ovirt1:iscsi1
[root at physical ~]# tgtadm --lld iscsi --op new --mode logicalunit --tid 3
--lun 1 -b /dev/VolGroup00/iSCSI3
[root at physical ~]# tgtadm --lld iscsi --op bind --mode target --tid 3 -I ALL

tgtadm shows the following information:

Target 3: ovirt1:iscsi1
    System information:
        Driver: iscsi
        State: ready
    I_T nexus information:
    LUN information:
        LUN: 0
            Type: controller
            SCSI ID: deadbeaf3:0
            SCSI SN: beaf30
            Size: 0 MB
            Online: Yes
            Removable media: No
            Backing store: No backing store
        LUN: 1
            Type: disk
            SCSI ID: deadbeaf3:1
            SCSI SN: beaf31
            Size: 16106 MB
            Online: Yes
            Removable media: No
            Backing store: /dev/VolGroup00/iSCSI3
    Account information:
    ACL information:
        ALL

I then go to the oVirt interface, click on default, Storage, Add Storage Server.

I choose:

Type: iSCSI
IP: 192.168.50.1
Port: Default
Target: ovirt1:iscsi1
and add it.

Upon switching to something else and back to the storage tab (seems like a
workaround to a 'bug' :P), I get the + icon next to 'iSCSI:
192.168.50.1:ovirt1:iscsi1'.

I then click on iSCSI: 192.168.50.1:ovirt:iscsi1:lun-1(15 GB) and choose
'Add New Volume'.

Size: 5 GB
LV Name: ovirttest
Permissions, all 0744

Which creates a node under the tree: 'LVM: ovirt_vg_5:ovirttest(5 GB)'
which has state showing as 'pending_setup'.

If I click on Tasks, and change the filter to All and All, I see a failed entry
for:

Type: StorageVolume
Item: LVM: ovirt_vg_5:ovirttest
Action: create_volume
State: failed
User: ovirtadmin
Created: recent timestamp
Args: <blank>
Message: Call to function virStoragePoolBuild failed

(note that these LVMs are impossible to delete)

They change to pending_deletion, action changes to 'delete_volume' and
virStoragePoolBuild is the same.

taskomatic.log has:

libvir: Storage error : invalid storage volume pointer in no storage vol with
matching path
refresh_pool
One of the logical volumes in VolGroup00 is not part of the pool of type
IscsiStoragePool that we are scanning; ignore the previous error!
done
libvir: error : internal error '/sbin/vgcreate ovirt_vg_5
/dev/disk/by-id/scsi-S_beaf31' exited with non-zero status 5 and signal 0:  
No physical volume label read from /dev/disk/by-id/scsi-S_beaf31
  /dev/disk/by-id/scsi-S_beaf31 not identified as an existing physical volume
  Unable to add physical volume '/dev/disk/by-id/scsi-S_beaf31' to
volume group 'ovirt_vg_5'.
create_volume
Task action processing failed: Libvirt::Error: Call to function
virStoragePoolBuild failed
/usr/share/ovirt-server/task-omatic/./utils.rb:62:in `build'
/usr/share/ovirt-server/task-omatic/./utils.rb:62:in `connect'
/usr/share/ovirt-server/task-omatic/./task_storage.rb:225:in `create_volume'
/usr/share/ovirt-server/task-omatic/taskomatic.rb:110
/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
done

I wonder if a step is been missed?

Regards,

Nigel