oslo.privsep

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

Bug #1735780 reported by James Anziano
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
os-brick
In Progress
Undecided
Rajat Dhasmana
oslo.privsep
Confirmed
Medium
Rajat Dhasmana

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/

Revision history for this message
Matt Riedemann (mriedem) wrote :

As far as I know, this test is passing in upstream CI at the moment, so which release of nova are you hitting this on, what is the setup involved, etc?

Changed in nova:
status: New → Incomplete
Revision history for this message
Matt Riedemann (mriedem) wrote :

Recent pass upstream:

http://logs.openstack.org/26/515426/1/check/legacy-tempest-dsvm-neutron-full/e6ac116/job-output.txt.gz#_2017-12-01_14_07_07_197785

Revision history for this message
Matt Riedemann (mriedem) wrote :

Oh I see, yeah, the test passes but we get errors in the logs:

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

Changed in nova:
status: Incomplete → Confirmed
Matt Riedemann (mriedem)
Changed in nova:
importance: Undecided → Medium
Revision history for this message
Matt Riedemann (mriedem) wrote :

(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.

summary: - n-cpu logs error "is not a valid LUKS device"
+ n-cpu logs error "is not a valid LUKS device" (at debug level)
Rajat Dhasmana (whoami-rajat)
Changed in nova:
assignee: nobody → Rajat Dhasmana (whoami-rajat)
Changed in oslo.privsep:
assignee: nobody → Rajat Dhasmana (whoami-rajat)
Rajat Dhasmana (whoami-rajat)
Changed in os-brick:
assignee: nobody → Rajat Dhasmana (whoami-rajat)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-brick (master)

Fix proposed to branch: master
Review: https://review.openstack.org/539487

Changed in os-brick:
status: New → In Progress
Revision history for this message
Lenny (lennyb) wrote :

I see similar error[1] (rocky version), but when I run tempest in loop it fails after few iteration.

 Stderr: u'Device /dev/disk/by-id/scsi-360000000000000000e00000000010001 is not a valid LUKS device.\nCommand failed with code 22: Invalid argument\n'

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-brick (master)

Change abandoned by Sean McGinnis (<email address hidden>) on branch: master
Review: https://review.openstack.org/539487
Reason: This review is > 4 weeks without comment and currently blocked by a core reviewer with a -2. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and contacting the reviewer with the -2 on this review to ensure you address their concerns.

Ben Nemec (bnemec)
Changed in oslo.privsep:
status: New → Confirmed
importance: Undecided → Medium
Lee Yarwood (lyarwood)
no longer affects: nova
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.