← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1914296] [NEW] tests involving encrypted volumes sometimes (rarely) fail with libvirtError: [...] Volume is not in LUKS format

 

Public bug reported:

Seen in the gate on a stable/ussuri change [1] where the test involving
encrypted volumes fails because of the following error and trace [2]:

Jan 27 23:53:10.926066 ubuntu-bionic-ovh-bhs1-0022752197 nova-
compute[19535]: ERROR nova.compute.manager [instance: f2218cab-1957
-419d-82a3-41aeeddee04f] libvirt.libvirtError: internal error: process
exited while connecting to monitor: 2021-01-27T23:53:10.255296Z qemu-
system-x86_64: -drive file=/dev/disk/by-id/scsi-
360000000000000000e00000000010001,key-secret=virtio-disk0-luks-
secret0,format=luks,if=none,id=drive-virtio-disk0,cache=none,aio=native:
Volume is not in LUKS format

Logstash query showing one other change hit on stable/victoria in
TestEncryptedCinderVolumes:

[None req-88bda522-cf3b-4af0-a770-a74a7283e3dd tempest-
TestEncryptedCinderVolumes-1578841671 tempest-
TestEncryptedCinderVolumes-1578841671-project] Exception during message
handling: libvirt.libvirtError: internal error: unable to execute QEMU
command 'blockdev-add': Volume is not in LUKS format

Logstash query:

http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22volume%20is%20not%20in%20luks%20format%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d

I'm not sure how the trace can say both "format=luks" and "Volume is not
in LUKS format" at the same time :\

[1] https://review.opendev.org/c/openstack/nova/+/761810
[2] https://zuul.opendev.org/t/openstack/build/492ed08935e1488eb0a40cc6415c02fc/log/compute1/logs/screen-n-cpu.txt#30691

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: gate-failure volumes

** Description changed:

  Seen in the gate on a stable/ussuri change [1] where the test involving
- encrypted volumes fails because of the following error and trace:
+ encrypted volumes fails because of the following error and trace [2]:
  
  Jan 27 23:53:10.926066 ubuntu-bionic-ovh-bhs1-0022752197 nova-
  compute[19535]: ERROR nova.compute.manager [instance: f2218cab-1957
  -419d-82a3-41aeeddee04f] libvirt.libvirtError: internal error: process
  exited while connecting to monitor: 2021-01-27T23:53:10.255296Z qemu-
  system-x86_64: -drive file=/dev/disk/by-id/scsi-
  360000000000000000e00000000010001,key-secret=virtio-disk0-luks-
  secret0,format=luks,if=none,id=drive-virtio-disk0,cache=none,aio=native:
  Volume is not in LUKS format
  
  Logstash query showing one other change hit on stable/victoria in
  TestEncryptedCinderVolumes:
  
  [None req-88bda522-cf3b-4af0-a770-a74a7283e3dd tempest-
  TestEncryptedCinderVolumes-1578841671 tempest-
  TestEncryptedCinderVolumes-1578841671-project] Exception during message
  handling: libvirt.libvirtError: internal error: unable to execute QEMU
  command 'blockdev-add': Volume is not in LUKS format
  
  Logstash query:
  
  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22volume%20is%20not%20in%20luks%20format%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d
  
+ I'm not sure how the trace can say both "format=luks" and "Volume is not
+ in LUKS format" at the same time :\
+ 
  [1] https://review.opendev.org/c/openstack/nova/+/761810
+ [2] https://zuul.opendev.org/t/openstack/build/492ed08935e1488eb0a40cc6415c02fc/log/compute1/logs/screen-n-cpu.txt#30691

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

Title:
  tests involving encrypted volumes sometimes (rarely) fail with
  libvirtError: [...] Volume is not in LUKS format

Status in OpenStack Compute (nova):
  New

Bug description:
  Seen in the gate on a stable/ussuri change [1] where the test
  involving encrypted volumes fails because of the following error and
  trace [2]:

  Jan 27 23:53:10.926066 ubuntu-bionic-ovh-bhs1-0022752197 nova-
  compute[19535]: ERROR nova.compute.manager [instance: f2218cab-1957
  -419d-82a3-41aeeddee04f] libvirt.libvirtError: internal error: process
  exited while connecting to monitor: 2021-01-27T23:53:10.255296Z qemu-
  system-x86_64: -drive file=/dev/disk/by-id/scsi-
  360000000000000000e00000000010001,key-secret=virtio-disk0-luks-
  secret0,format=luks,if=none,id=drive-virtio-
  disk0,cache=none,aio=native: Volume is not in LUKS format

  Logstash query showing one other change hit on stable/victoria in
  TestEncryptedCinderVolumes:

  [None req-88bda522-cf3b-4af0-a770-a74a7283e3dd tempest-
  TestEncryptedCinderVolumes-1578841671 tempest-
  TestEncryptedCinderVolumes-1578841671-project] Exception during
  message handling: libvirt.libvirtError: internal error: unable to
  execute QEMU command 'blockdev-add': Volume is not in LUKS format

  Logstash query:

  http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22volume%20is%20not%20in%20luks%20format%5C%22%20AND%20tags%3A%5C%22screen-n-cpu.txt%5C%22&from=7d

  I'm not sure how the trace can say both "format=luks" and "Volume is
  not in LUKS format" at the same time :\

  [1] https://review.opendev.org/c/openstack/nova/+/761810
  [2] https://zuul.opendev.org/t/openstack/build/492ed08935e1488eb0a40cc6415c02fc/log/compute1/logs/screen-n-cpu.txt#30691

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


Follow ups