test_boot_server_from_encrypted_volume_luks has insufficient skip decorator

Bug #1702843 reported by Silvan Kaiser on 2017-07-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

test_boot_server_from_encrypted_volume_luks tests attaching an encrypted volume. This is not supported by several remotefs drivers (support=False is actually the remotefs default setting). However the test as introduced in [1] skips only for ceph and nfs making other drivers based on the remotefs driver (e.g. Quobyte) fail this tempest test.

Afaics there's no way to deactivate the test via tempest config, althought I'd thought that attach_encrypted_volume=False should be applied to this test, no?
Otherwise the skip decorator on test_boot_server_from_encrypted_volume_luks needs to be extended to cover other affected drivers, too.

[1] https://review.openstack.org/#/c/472219

zhufl (zhu-fanglei) wrote :

I'd like to know:
1. if attach_encrypted_volume is not supported in one system, can we think that
   boot_server_from_encrypted_volume will also not be supported in that system?
2. is attach_encrypted_volume supported for ceph and nfs?

Ghanshyam Mann (ghanshyammann) wrote :

Current condition to skip this tests is not good and does not cover all cases.

Either we should use existing config option 'attach_encrypted_volume' or add new one. We need to check and confirm whether both feature 1. attach encrypted volume and 2. boot server from encrypted volume is same things.

If so then we can use 'attach_encrypted_volume' flag to skip this test. and ceph and nfs plugin can set that accordingly.

Changed in tempest:
status: New → Triaged
importance: Undecided → Low
Silvan Kaiser (2-silvan) wrote :

I do not know the exact change but the test is now skipped ok according to no LUKS support settings. Issue solved.

Changed in tempest:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers