Re: [Users] could not add iscsi disk in ovirt.

On 27/09/13 19:52, Dafna Ron wrote: > wait :) > > the first screen shot was of local storage and internal disk type - > not related at all to the direct lun feature. > > the second screen shot is for iscsi storage pool. > it shows a current connected lun that you have. > > try this: > > create a new target lun. > log in to the webadmin -> disks tab -> new disk > select the Default DC (which is your iscsi storage type) -> expend > the "discover tartest" > put in your storage server (where you created the lun) -> discover > you should than see a list of targets -> log in > select the target and press OK. > > > On 09/27/2013 03:11 PM, Saurabh wrote: >> On 27/09/13 19:14, Dafna Ron wrote: >>> the output is empty in both your outpit and the logs. >>> >>> This is the part in the log that shows that you do not have any >>> devices: return: [] >>> >>> when you create a new disk and select the NFS DC- can you please >>> send me the screen shot of that? >>> >>> >>> On 09/27/2013 02:41 PM, Saurabh wrote: >>>> On 27/09/13 18:40, Dafna Ron wrote: >>>>> I am not sure direct lun will be supported for an NFS pool... can >>>>> you try the same from iscsi pool? >>>>> >>>>> is this lun being used somewhere else or did you create a new one? >>>>> you can run vdsClient -s 0 getDeviceList to see the list of the >>>>> available luns and if the status is free or not. >>>>> (it should also in the logs (engine and vdsm) when you discover >>>>> the luns from the webadmin. >>>>> >>>>> >>>>> On 09/27/2013 01:43 PM, Saurabh wrote: >>>>>> >>>>>> Hi guys, I am running ovirt with NFS as storage pool. Everything >>>>>> is working quite fine for me. The only problem is I could not >>>>>> add the a new iscsi disk in Disk tab. When I go to the Disk tab >>>>>> there is an option of adding new disk from internal storage and >>>>>> another option is add External (Direct Lun). When I opt for the >>>>>> External (Direct LUN), I am able to discover the Lun but could >>>>>> not log in to that lun using the ovirt web console. Whereas when >>>>>> I try to login to that lun using the isciadm in command line I >>>>>> am able to login. Any help?? >>>>>> >>>>>> _______________________________________________ >>>>>> Users mailing list >>>>>> Users(a)ovirt.org >>>>>> http://lists.ovirt.org/mailman/listinfo/users >>>>> >>>>> >>>> I have created a new Lun for this purpose only and it is not being >>>> used anywhere. >>>> In order to try an iscsi pool I will have to reconfigure the >>>> engine, because during the engine setup I opted for nfs. >>>> >>>> This is the output when I run this command. >>>> >>>> [root@ovirt ~]# vdsClient -s 0 getDeviceList >>>> [] >>>> >>>> >>>> >>>> >>>> >>>> this is log snippet from engine.log when I discover and try to >>>> login to that lun. >>>> >>>> >>>> ################################################################################################# >>>> >>>> 013-09-27 14:34:55,592 INFO >>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] >>>> (ajp--127.0.0.1-8702-11) START, >>>> DiscoverSendTargetsVDSCommand(HostName = 192.168.100.59, HostId = >>>> 168842b9-071b-4c64-a22d-07ae1e63830b, connection={ id: null, >>>> connection: 192.168.100.160, iqn: null, vfsType: null, >>>> mountOptions: null, nfsVersion: null, nfsRetrans: null, nfsTimeo: >>>> null };), log id: 2e12b97 >>>> 2013-09-27 14:34:55,653 INFO >>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.DiscoverSendTargetsVDSCommand] >>>> (ajp--127.0.0.1-8702-11) FINISH, DiscoverSendTargetsVDSCommand, >>>> return: [{ id: null, connection: 192.168.100.160, iqn: >>>> iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: >>>> null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };], log >>>> id: 2e12b97 >>>> 2013-09-27 14:36:25,877 INFO >>>> [org.ovirt.engine.core.bll.storage.ConnectStorageToVdsCommand] >>>> (ajp--127.0.0.1-8702-2) Running command: >>>> ConnectStorageToVdsCommand internal: false. Entities affected : >>>> ID: aaa00000-0000-0000-0000-123456789aaa Type: System >>>> 2013-09-27 14:36:25,880 INFO >>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] >>>> (ajp--127.0.0.1-8702-2) START, >>>> ConnectStorageServerVDSCommand(HostName = 192.168.100.59, HostId = >>>> 168842b9-071b-4c64-a22d-07ae1e63830b, storagePoolId = >>>> 00000000-0000-0000-0000-000000000000, storageType = ISCSI, >>>> connectionList = [{ id: null, connection: 192.168.100.160, iqn: >>>> iqn.2013.26.ovirt.techblue.lv001, vfsType: null, mountOptions: >>>> null, nfsVersion: null, nfsRetrans: null, nfsTimeo: null };]), log >>>> id: 5fca13a4 >>>> 2013-09-27 14:36:26,012 INFO >>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.ConnectStorageServerVDSCommand] >>>> (ajp--127.0.0.1-8702-2) FINISH, ConnectStorageServerVDSCommand, >>>> return: {00000000-0000-0000-0000-000000000000=0}, log id: 5fca13a4 >>>> 2013-09-27 14:36:26,098 INFO >>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (ajp--127.0.0.1-8702-12) >>>> START, GetDeviceListVDSCommand(HostName = 192.168.100.59, HostId = >>>> 168842b9-071b-4c64-a22d-07ae1e63830b, storageType=ISCSI), log id: >>>> 20fb893b >>>> 2013-09-27 14:36:29,376 INFO >>>> [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (ajp--127.0.0.1-8702-12) >>>> FINISH, GetDeviceListVDSCommand, return: [], log id: 20fb893b >>>> >>>> ###################################################################################################### >>>> >>>> >>>> >>>> >>> >>> >> Here I am sending you the two screenshots, one is when I am adding >> the disk from the Local-storage that is NFS, and another is the >> Direct lun. >> You can see that I am able to discover it but could not log into it. >> > > ok so there is no means we can use an iscsi disk in a Data center whoose default storage is NFS?