Descriptionvvyazmin@redhat.com
2013-02-12 20:58:52 UTC
Created attachment 696617[details]
## Logs vdsm, rhevm, screen-shots
Description of problem:
Failed create Direct LUN via Guide Me option
Version-Release number of selected component (if applicable):
RHEVM 3.2 - SF06 environment:
RHEVM: rhevm-3.2.0-7.el6ev.noarch
VDSM: vdsm-4.10.2-7.0.el6ev.x86_64
LIBVIRT: libvirt-0.10.2-18.el6.x86_64
QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64
SANLOCK: sanlock-2.6-2.el6.x86_64
How reproducible:
100%
Steps to Reproduce:
1. On FC environment, create VM via Guide Me
2. Create a new Direct LUN via Guide Me
Actual results:
1. Failed create Direct LUN via Guide Me option on FC environment only
2. Get error:
Cannot add Virtual Machine Disk. The provided lun has no valid lun type.
3. No problem found in iSCSI environment
4. No problem add / create a new Direct LUN via Disks tab
Expected results:
Succeed create Direct LUN via Guide Me option
Additional info:
/var/log/ovirt-engine/engine.log
2013-02-12 23:57:30,175 INFO [org.ovirt.engine.core.bll.AddDiskCommand] (ajp-/127.0.0.1:8702-14) [c7aec79] Lock Acquired to object EngineLock [exclusiveLocks= , sharedLocks= key: 374a6cba-f641-406d-8e98-fb3460bb1c23 value: VM
]
2013-02-12 23:57:30,186 WARN [org.ovirt.engine.core.bll.AddDiskCommand] (ajp-/127.0.0.1:8702-14) [c7aec79] CanDoAction of action AddDisk failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__VM_DISK,ACTION_TYPE_FAILED_DISK_LUN_HAS_NO_VALID_TYPE
2013-02-12 23:57:30,186 INFO [org.ovirt.engine.core.bll.AddDiskCommand] (ajp-/127.0.0.1:8702-14) [c7aec79] Lock freed to object EngineLock [exclusiveLocks= , sharedLocks= key: 374a6cba-f641-406d-8e98-fb3460bb1c23 value: VM
/var/log/vdsm/vdsm.log
Comment 4vvyazmin@redhat.com
2013-02-17 10:35:53 UTC
Created attachment 696617 [details] ## Logs vdsm, rhevm, screen-shots Description of problem: Failed create Direct LUN via Guide Me option Version-Release number of selected component (if applicable): RHEVM 3.2 - SF06 environment: RHEVM: rhevm-3.2.0-7.el6ev.noarch VDSM: vdsm-4.10.2-7.0.el6ev.x86_64 LIBVIRT: libvirt-0.10.2-18.el6.x86_64 QEMU & KVM: qemu-kvm-rhev-0.12.1.2-2.348.el6.x86_64 SANLOCK: sanlock-2.6-2.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1. On FC environment, create VM via Guide Me 2. Create a new Direct LUN via Guide Me Actual results: 1. Failed create Direct LUN via Guide Me option on FC environment only 2. Get error: Cannot add Virtual Machine Disk. The provided lun has no valid lun type. 3. No problem found in iSCSI environment 4. No problem add / create a new Direct LUN via Disks tab Expected results: Succeed create Direct LUN via Guide Me option Additional info: /var/log/ovirt-engine/engine.log 2013-02-12 23:57:30,175 INFO [org.ovirt.engine.core.bll.AddDiskCommand] (ajp-/127.0.0.1:8702-14) [c7aec79] Lock Acquired to object EngineLock [exclusiveLocks= , sharedLocks= key: 374a6cba-f641-406d-8e98-fb3460bb1c23 value: VM ] 2013-02-12 23:57:30,186 WARN [org.ovirt.engine.core.bll.AddDiskCommand] (ajp-/127.0.0.1:8702-14) [c7aec79] CanDoAction of action AddDisk failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__VM_DISK,ACTION_TYPE_FAILED_DISK_LUN_HAS_NO_VALID_TYPE 2013-02-12 23:57:30,186 INFO [org.ovirt.engine.core.bll.AddDiskCommand] (ajp-/127.0.0.1:8702-14) [c7aec79] Lock freed to object EngineLock [exclusiveLocks= , sharedLocks= key: 374a6cba-f641-406d-8e98-fb3460bb1c23 value: VM /var/log/vdsm/vdsm.log