Already started talking Matt Treinish about this on IRC last week. Unsure where the fix should actual go into. 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 TestEncryptedCi nderVolumes tests:
{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- TestEncryptedCi nderVolumes- 676292884: 01:sn:aef6a6f1c d84768f- lun-0
Already started talking Matt Treinish about this on IRC last week. Unsure where the fix should actual go into. 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.