[Users] Adding LIO iSCSI target as storage fails

Thu Nov 22 16:40:24 UTC 2012

----- Original Message -----
> From: "Vincent Miszczak" <vmiszczak at ankama.com>
> To: "Eli Mesika" <emesika at redhat.com>
> Cc: users at ovirt.org
> Sent: Thursday, November 22, 2012 3:49:55 PM
> Subject: RE: [Users] Adding LIO iSCSI target as storage fails
> 
> Done as :
> https://bugzilla.redhat.com/show_bug.cgi?id=879272

Thanks , a patch resolving that was already posted.

> 
> -----Message d'origine-----
> De : Eli Mesika [mailto:emesika at redhat.com]
> Envoyé : jeudi 22 novembre 2012 13:31
> À : Vincent Miszczak
> Cc : users at ovirt.org
> Objet : Re: [Users] Adding LIO iSCSI target as storage fails
> 
> 
> 
> ----- Original Message -----
> > From: "Vincent Miszczak" <vmiszczak at ankama.com>
> > To: users at ovirt.org
> > Sent: Thursday, November 22, 2012 12:45:11 PM
> > Subject: Re: [Users] Adding LIO iSCSI target as storage fails
> > 
> > 
> > 
> > 
> > 
> > Hi again,
> > 
> > 
> > 
> > Having fixed LUNs and LUN_storage_server_connection_map tables
> > varchar
> > sizes, adding my LIO storage is OK as expected.
> 
> Hi Vincent
> Can you open a BZ on that in order to resize the iqn column in
> storage_server_connection table ?
> Thanks
> 
> Eli Mesika
> 
> > 
> > 
> > 
> > create_tables.sql script should be fixed.
> > 
> > 
> > 
> > What’s more, when the error happened, ovirt got in inconsistent
> > state
> > :
> > 
> > -the LUN appeared in ovirt but was locked. Trying to destroy it did
> > nothing in the GUI. Engine logged “Failed to Acquire Lock to object
> > EngineLock”. After a while, the LUN disappeared by itself.
> > 
> > 
> > 
> > Ovirt should handle the exception correctly (by totally refusing
> > the
> > LUN registration) and outputting an explicit message (instead of
> > “error 503”) could be nice.
> > 
> > 
> > 
> > Vince
> > 
> > 
> > 
> > 
> > 
> > De : Vincent Miszczak
> > Envoyé : jeudi 22 novembre 2012 10:25
> > À : users at ovirt.org
> > Objet : Adding LIO iSCSI target as storage fails
> > 
> > 
> > 
> > Hi guys,
> > 
> > 
> > 
> > I’m trying to add an LIO iSCSI target as data domain into ovirt and
> > it
> > fails.
> > 
> > 
> > 
> > The GUI reports :
> > 
> > Error: A Request to the Server failed with the following Status
> > Code:
> > 503
> > 
> > 
> > 
> > And the engine log reports :
> > 
> > 2012-11-22 10:05:10,154 INFO
> > [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] Running command:
> > AddSANStorageDomainCommand internal: false. Entities affected : ID:
> > aaa00000-0000-0000-0000-123456789aaa Type: System
> > 
> > 2012-11-22 10:05:10,177 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVGVDSCommand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] START, CreateVGVDSCommand(vdsId =
> > 936326ca-3482-11e2-a6fc-6f050df067da,
> > storageDomainId=6e93ed9e-1dd7-42b7-9e93-dc0187cc6fde,
> > deviceList=[50103ff106001405db2776165d33492091bde115a020100344c494f2d4
> > f52470049424c4f434b3a64623237373631362d356433332d343932302d393162642d]
> > ),
> > log id: 7bbd158c
> > 
> > 2012-11-22 10:05:10,904 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateVGVDSCommand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] FINISH, CreateVGVDSCommand,
> > return:
> > LvKD1i-L68S-ix09-OYcr-Ytzd-93wh-8XFe8e, log id: 7bbd158c
> > 
> > 2012-11-22 10:05:10,913 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStorageDomainVDSComma
> > nd]
> > (ajp--0.0.0.0-8009-3) [7ff25919] START,
> > CreateStorageDomainVDSCommand(vdsId =
> > 936326ca-3482-11e2-a6fc-6f050df067da,
> > storageDomain=org.ovirt.engine.core.common.businessentities.storage_do
> > main_static at cd3431b , args=LvKD1i-L68S-ix09-OYcr-Ytzd-93wh-8XFe8e),
> > log id: 56c4cbde
> > 
> > 2012-11-22 10:05:17,332 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.CreateStorageDomainVDSComma
> > nd]
> > (ajp--0.0.0.0-8009-3) [7ff25919] FINISH,
> > CreateStorageDomainVDSCommand, log id: 56c4cbde
> > 
> > 2012-11-22 10:05:17,338 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStorageDomainStatsVDSCom
> > mand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] START,
> > GetStorageDomainStatsVDSCommand(vdsId =
> > 936326ca-3482-11e2-a6fc-6f050df067da,
> > storageDomainId=6e93ed9e-1dd7-42b7-9e93-dc0187cc6fde), log id:
> > 5142061
> > 
> > 2012-11-22 10:05:17,654 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetStorageDomainStatsVDSCom
> > mand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] FINISH,
> > GetStorageDomainStatsVDSCommand, return:
> > org.ovirt.engine.core.common.businessentities.storage_domains at 68e03e79
> > , log id: 5142061
> > 
> > 2012-11-22 10:05:17,674 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] START, GetVGInfoVDSCommand(vdsId =
> > 936326ca-3482-11e2-a6fc-6f050df067da,
> > VGID=LvKD1i-L68S-ix09-OYcr-Ytzd-93wh-8XFe8e), log id: 52756b80
> > 
> > 2012-11-22 10:05:17,739 INFO
> > [org.ovirt.engine.core.vdsbroker.vdsbroker.GetVGInfoVDSCommand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] FINISH, GetVGInfoVDSCommand,
> > return:
> > [org.ovirt.engine.core.common.businessentities.LUNs at 53a8c83f], log
> > id: 52756b80
> > 
> > 2012-11-22 10:05:17,758 INFO
> > [org.ovirt.engine.core.utils.transaction.TransactionSupport]
> > (ajp--0.0.0.0-8009-3) [7ff25919] transaction rolled back
> > 
> > 2012-11-22 10:05:17,759 ERROR
> > [org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand]
> > (ajp--0.0.0.0-8009-3) [7ff25919] Command
> > org.ovirt.engine.core.bll.storage.AddSANStorageDomainCommand throw
> > exception: org.springframework.dao.DataIntegrityViolationException:
> > CallableStatementCallback; SQL [{call insertluns(?, ?, ?, ?, ?, ?,
> > ?,
> > ?)}]; ERROR: value too long for type character varying(50)
> > 
> > Where: SQL statement "INSERT INTO LUNs(LUN_id, physical_volume_id,
> > volume_group_id, serial, lun_mapping, vendor_id, product_id,
> > device_size) VALUES( $1 , $2 , $3 , $4 , $5 , $6 , $7 , $8 )"
> > 
> > PL/pgSQL function "insertluns" line 2 at SQL statement; nested
> > exception is org.postgresql.util.PSQLException: ERROR: value too
> > long
> > for type character varying(50)
> > 
> > Where: SQL statement "INSERT INTO LUNs(LUN_id, physical_volume_id,
> > volume_group_id, serial, lun_mapping, vendor_id, product_id,
> > device_size) VALUES( $1 , $2 , $3 , $4 , $5 , $6 , $7 , $8 )"
> > 
> > 
> > 
> > Being registered to LIO mailing list, I know there are concerns
> > about
> > LUN ID length being pretty insane (127 chars here). Having used an
> > Equallogic iSCSI SAN, I did not have this problem, so I suppose
> > this
> > come from the id length. Until this is fixed at LIO side (if it has
> > to
> > be), ovirt should handle such situations.
> > 
> > 
> > 
> > I’m gonna resize my database col size to test that.
> > 
> > 
> > 
> > My configuration :
> > 
> > oVirt Engine Version: 3.1.0-3.19.el6 (Dreyou repo) running on stock
> > Centos6.3
> > 
> > LIO Target running on Centos6.3/3.6.3-1.el6.elrepo.x86_64 kernel
> > 
> > Ovirt node running on latest Fedora17
> > 
> > 
> > 
> > Vince
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner , and is believed to be clean.
> > _______________________________________________
> > Users mailing list
> > Users at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/users
> > 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 