action #69751
closed[y] Module validate_encrypt fails on s390x-kvm-sle12
0%
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
Updated by riafarov over 3 years ago
- Has duplicate action #69991: [y] test fails in validate_encrypt added
Updated by ybonatakis over 3 years ago
- Status changed from Workable to In Progress
- Assignee set to ybonatakis
Updated by ybonatakis over 3 years ago
Updated by ybonatakis over 3 years 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
Updated by ybonatakis over 3 years ago
- Status changed from In Progress to Feedback
Updated by ybonatakis over 3 years 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.
Updated by ybonatakis over 3 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10923 and also i own a PR for the jobgroup yaml
Updated by ybonatakis over 3 years ago
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/10927 last one with the missing piece for cryptlvm_iscsi
Updated by ybonatakis over 3 years 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
Updated by ybonatakis over 3 years ago
- Assignee changed from ybonatakis to JERiveraMoya
Updated by JERiveraMoya over 3 years ago
Please, do not assign tickets to anybody without talking with the person first. Leave them unsigned is the way we normally do.
Updated by riafarov over 3 years ago
- Assignee set to riafarov
Taking over to see if anything is left to fix.
Updated by riafarov over 3 years ago
https://openqa.opensuse.org/tests/1380490 got broken too, as well as https://openqa.opensuse.org/tests/1380433
Updated by riafarov over 3 years 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.
Updated by JERiveraMoya about 3 years ago
- Status changed from Feedback to Resolved