yahoo-eng-team team mailing list archive

[Mike Perez <thingee@xxxxxxxxx>]

Public bug reported:

When running Datera storage with Cinder and the following
TestEncryptedCinderVolumes tests:

{0} tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_cryptsetup 
{0} tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_luks

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-
TestEncryptedCinderVolumes-676292884:01:sn:aef6a6f1cd84768f-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.

** Affects: cinder
     Importance: Undecided
         Status: New

** Affects: nova
     Importance: Undecided
         Status: New

** Affects: tempest
     Importance: Undecided
         Status: New

** Also affects: cinder
   Importance: Undecided
       Status: New

** Also affects: nova
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1432490

Title:
  TestEncryptedCinderVolumes cryptsetup name is too long

Status in Cinder:
  New
Status in OpenStack Compute (Nova):
  New
Status in Tempest:
  New

Bug description:
  When running Datera storage with Cinder and the following
  TestEncryptedCinderVolumes tests:

  {0} tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_cryptsetup 
  {0} tempest.scenario.test_encrypted_cinder_volumes.TestEncryptedCinderVolumes.test_encrypted_cinder_volumes_luks

  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-
  TestEncryptedCinderVolumes-676292884:01:sn:aef6a6f1cd84768f-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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1432490/+subscriptions