yahoo-eng-team team mailing list archive

[James Anziano <janzian@xxxxxxxxxx>]

Public bug reported:

Probably easiest way to reproduce this is to run the tempest test
tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_boot_server_from_encrypted_volume_luks.
The test passes successfully, but will produce an error in the n-cpu
logs during the server creation. This may also be indicative that even
though the test passes, it is not working as intended, but I don't
believe this is the case (from what I've been able to tell, the server
creation is successful and the volume is properly encrypted at all
stages of the test). Logs attached [1].

[1] http://paste.openstack.org/show/627976/

** Affects: nova
     Importance: Undecided
         Status: Incomplete

-- 
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/1735780

Title:
  n-cpu logs error "is not a valid LUKS device"

Status in OpenStack Compute (nova):
  Incomplete

Bug description:
  Probably easiest way to reproduce this is to run the tempest test
  tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_boot_server_from_encrypted_volume_luks.
  The test passes successfully, but will produce an error in the n-cpu
  logs during the server creation. This may also be indicative that even
  though the test passes, it is not working as intended, but I don't
  believe this is the case (from what I've been able to tell, the server
  creation is successful and the volume is properly encrypted at all
  stages of the test). Logs attached [1].

  [1] http://paste.openstack.org/show/627976/

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