Project

General

Profile

action #69751

[y] Module validate_encrypt fails on s390x-kvm-sle12

Added by syrianidou_sofia about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - SLE 15 SP3
Start date:
2020-08-10
Due date:
2020-09-08
% Done:

0%

Estimated time:
5.00 h
Difficulty:

Description

Observation

Seems to be related to https://github.com/os-autoinst/os-autoinst-distri-opensuse/commit/0dabd841cf1cd34f5fb78e17970f08d1a97574f6

openQA test in scenario sle-15-SP3-Online-s390x-lvm-encrypt-separate-boot@s390x-kvm-sle12 fails in
validate_encrypt

It's just zkvm affected

openQA test in scenario sle-15-SP2-Online-s390x-lvm-full-encrypt@s390x-kvm-sle12 and lvm-encrypt-separate-boot@s390x-kvm-sle12 fails in
validate_encrypt
or
validate_encrypt

Looks like the command

command 'cryptsetup -v luksHeaderBackup /dev/disk/by-path/ccw-0.0.0000-part3 --header-backup-file /root//dev/disk/by-path/ccw-0.0.0000-part3

needs some modification for the particular machine.

The failure message is the bellow

# Test died: command 'cryptsetup -v luksHeaderBackup /dev/disk/by-path/ccw-0.0.0000-part3 --header-backup-file /root//dev/disk/by-path/ccw-0.0.0000-part3' failed at /var/lib/openqa/cache/openqa.suse.de/tests/sle/lib/validate_encrypt_utils.pm line 92.

Expected result

Last good: 209.2 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues

Has duplicate openQA Tests - action #69991: [y] test fails in validate_encryptRejected2020-08-13

History

#1 Updated by riafarov about 1 year ago

  • Description updated (diff)
  • Due date set to 2020-09-08
  • Priority changed from Normal to High
  • Estimated time set to 5.00 h

Using this ticket and resolving #69991 as duplicate.

#2 Updated by riafarov about 1 year ago

  • Has duplicate action #69991: [y] test fails in validate_encrypt added

#3 Updated by riafarov about 1 year ago

  • Target version set to SLE 15 SP3

#4 Updated by riafarov about 1 year ago

  • Status changed from New to Workable

#5 Updated by ybonatakis about 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to ybonatakis

#7 Updated by ybonatakis about 1 year ago

The code used the encrypted-device path from the crypttab output. The path could be
either the underlying block device or file, or a specification of a block device with a UUID.
So the luksHeaderBackup and luksHeaderRestore used to use for the binary backup file a
structure like /roor/UUID=. In the case of s390x the structure was root/.
I think the reason of the failure is that the --header-backup-file expects a new file in an
existing path.
Because for both cases this looks wrong to me i copy the backup_path that it was being used before
the refactoring. The current approach pass /root/bkp_luks_header_
in --header-backup-file of luksHeaderBackup and luksHeaderRestore for all the test_suites

#8 Updated by ybonatakis about 1 year ago

  • Status changed from In Progress to Feedback

#9 Updated by ybonatakis about 1 year ago

  • Status changed from Feedback to Resolved

looks good on osd

#11 Updated by ybonatakis about 1 year ago

  • Status changed from Resolved to In Progress

reopen it to fix the issues that the PR causes to some group of jobs. The fix is related to the backup_base_path that is missing from some. we need to adjust also the test_data in the cases that they have multi-encryption.

#13 Updated by ybonatakis about 1 year ago

https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10927 last one with the missing piece for cryptlvm_iscsi

#14 Updated by ybonatakis about 1 year ago

  • Status changed from In Progress to Feedback

https://openqa.suse.de/tests/4624966 for the cryptlvm_iscsi pass. you can close the ticket once the the PR is merged. i assigned it to @joaquin, as i will not be here tomorrow

#15 Updated by ybonatakis about 1 year ago

  • Assignee changed from ybonatakis to JERiveraMoya

#16 Updated by JERiveraMoya about 1 year ago

Please, do not assign tickets to anybody without talking with the person first. Leave them unsigned is the way we normally do.

#17 Updated by JERiveraMoya about 1 year ago

  • Assignee deleted (JERiveraMoya)

#18 Updated by riafarov about 1 year ago

  • Assignee set to riafarov

Taking over to see if anything is left to fix.

#20 Updated by riafarov about 1 year ago

Fixed by setting YAML_TEST_DATA=test_data/yast/encryption/lvm_encrypt_separate_boot.yaml

Keeping the ticket open in case something else pop-up up.

#21 Updated by JERiveraMoya about 1 year ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF