yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

(10:08:04 AM) mriedem: lyarwood: https://bugs.launchpad.net/nova/+bug/1735780
(10:08:06 AM) openstack: Launchpad bug 1735780 in OpenStack Compute (nova) "n-cpu logs error "is not a valid LUKS device"" [Undecided,Confirmed]
(10:08:10 AM) mriedem: http://logs.openstack.org/26/515426/1/check/legacy-tempest-dsvm-neutron-full/e6ac116/logs/screen-n-cpu.txt.gz#_Dec_01_14_06_49_142977
(10:17:18 AM) lyarwood: mriedem: looking
(10:19:08 AM) lyarwood: mriedem: so that's normal, search for cryptsetup below that and you can see we format and then open it correctly
(10:19:27 AM) mriedem: lyarwood: :(
(10:19:36 AM) mriedem: i guess that's why it's a stacktrace at debug rather than error?
(10:19:45 AM) mriedem: which is i think a thing i've seen with privsep before
(10:20:13 AM) lyarwood: https://github.com/openstack/os-brick/blob/master/os_brick/encryptors/luks.py#L150-L161
(10:20:36 AM) lyarwood: mriedem: yeah I think so

So this might just be a problem in the oslo.privsep library where it
dumps stacktraces at debug level which aren't actually errors.

** Also affects: oslo.privsep
   Importance: Undecided
       Status: New

** Summary changed:

- n-cpu logs error "is not a valid LUKS device"
+ n-cpu logs error "is not a valid LUKS device" (at debug level)

-- 
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" (at debug level)

Status in OpenStack Compute (nova):
  Confirmed
Status in oslo.privsep:
  New

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