We had to skip these tests in our CI as well. Our EqualLogic array's IQNs are too long as well.
-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Walt Boring
Sent: Tuesday, April 07, 2015 2:12 PM
To: McGinnis, Sean
Subject: [Bug 1432490] Re: TestEncryptedCinderVolumes cryptsetup name is too long
For what it's worth, HP Lefthand Volume IQN's are just as long as
Datera's. Cinder/Openstack cannot enforce length restriction on iSCSI
array vendor's IQN length.
Title:
TestEncryptedCinderVolumes cryptsetup name is too long
Status in Cinder:
Invalid
Status in OpenStack Compute (Nova):
Invalid
Status in Tempest:
Invalid
Bug description:
First off, while I understand this is not reproducible with the
reference implementation LVM, this seems like a unknown limitation
today since we're not enforcing any length on the IQN or recommending
anything.
When running Datera storage with Cinder and the following
TestEncryptedCinderVolumes tests:
Dell - Internal Use - Confidential
We had to skip these tests in our CI as well. Our EqualLogic array's IQNs are too long as well.
-----Original Message----- nderVolumes cryptsetup name is too long
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Walt Boring
Sent: Tuesday, April 07, 2015 2:12 PM
To: McGinnis, Sean
Subject: [Bug 1432490] Re: TestEncryptedCi
For what it's worth, HP Lefthand Volume IQN's are just as long as
Datera's. Cinder/Openstack cannot enforce length restriction on iSCSI
array vendor's IQN length.
-- /bugs.launchpad .net/bugs/ 1432490
You received this bug notification because you are subscribed to a
duplicate bug report (1440187).
https:/
Title: CinderVolumes cryptsetup name is too long
TestEncrypted
Status in Cinder:
Invalid
Status in OpenStack Compute (Nova):
Invalid
Status in Tempest:
Invalid
Bug description:
First off, while I understand this is not reproducible with the
reference implementation LVM, this seems like a unknown limitation
today since we're not enforcing any length on the IQN or recommending
anything.
When running Datera storage with Cinder and the following CinderVolumes tests:
TestEncrypted
{0} tempest. scenario. test_encrypted_ cinder_ volumes. TestEncryptedCi nderVolumes. test_encrypted_ cinder_ volumes_ cryptsetup scenario. test_encrypted_ cinder_ volumes. TestEncryptedCi nderVolumes. test_encrypted_ cinder_ volumes_ luks
{0} tempest.
cryptsetup complains about the name being too long:
http:// paste.openstack .org/show/ 192537
Nova uses the device name that's in /dev/disk-by-path, which in this
case is the returned iqn from the backend:
ip-172. 30.128. 2:3260- iscsi-iqn. 2013-05. com.daterainc: OpenStack- CinderVolumes- 676292884: 01:sn:aef6a6f1c d84768f- lun-0
TestEncrypted
Already started talking Matt Treinish about this on IRC last week.
Unsure where the fix should actual go into.
To manage notifications about this bug go to: /bugs.launchpad .net/cinder/ +bug/1432490/ +subscriptions
https:/