TestEncryptedCinderVolumes cryptsetup name is too long
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Invalid
|
Undecided
|
Unassigned | ||
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned | ||
tempest |
Invalid
|
Undecided
|
Unassigned |
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 TestEncryptedCi
{0} tempest.
{0} tempest.
cryptsetup complains about the name being too long:
http://
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.
Already started talking Matt Treinish about this on IRC last week. Unsure where the fix should actual go into.
This seems to be causing a lot of confusion for people; The issue is only being seen by Datera right now because of the way it forms it's IQN using the display-name of the volume which is ridiculously long in this test case.
This should probably use the UUID of the volume and a prefix like we do in the LVM driver and others. Especially since we don't enforce unique display-names.