coordination #28504: [sle][functional][epic] crypt lvm for SLE 12-SP3, SLE 12-SP4 and SLE 15 - openQA Tests - openSUSE Project Management Tool

Actions

Copy link

coordination #28504

closed

[sle][functional][epic] crypt lvm for SLE 12-SP3, SLE 12-SP4 and SLE 15

Added by SLindoMansilla over 6 years ago. Updated over 3 years ago.

Status:

Resolved

Priority:

Urgent

Assignee:

SLindoMansilla

Category:

Bugs in existing tests

Target version:

openQA Project - Milestone 14

Start date:

2017-09-18

Due date:

2018-02-27

% Done:

100%

Estimated time:

(Total: 0.00 h)

Difficulty:

Description

Acceptance criteria¶

AC1: All the sub tasks are resolved or rejected.

Related bugs¶

bsc#1062806 - openQA test fails in boot_encrypt - AArch64 cannot boot from encrypted LVM
bsc#1067481 - passphrase for the password is asked in text, instead of gui on arm and x86_64 due to dropped plymouth
bsc#1067479 - passphrase is asked twice when encrypt root partition on arm and x86_64
bsc#1070139 - Not needed boot partition is added extra, causing it to not be encrypted

Related features¶

fate#320901 - Provide kernel interface to pass LUKS password from bootloader

Collection of affected and related jobs¶

SLE 12-SP4 aarch¶

N/A

SLE 12-SP4 ppc¶

N/A

SLE 12-SP4 x86_64¶

N/A

SLE 15 349.1 aarch¶

osd#1268571#step/partitioning_lvm/7
osd#1268571#step/grub_test/1 password asked
N/A
- bsc#1062806 - openQA test fails in boot_encrypt - AArch64 cannot boot from encrypted LVM
- bsc#1067481 - passphrase for the password is asked in text, instead of gui on arm and x86_64 due to dropped plymouth
- bsc#1067479 - passphrase is asked twice when encrypt root partition on arm and x86_64

SLE 15 349.1 ppc¶

osd#1268728#step/partitioning_lvm/7
osd#1268728#step/grub_test/1 no password asked
- bsc#1070139 - Not needed boot partition is added extra, causing it to not be encrypted
osd#1268728#step/boot_encrypt/1 password asked
- bsc#1067479 - passphrase is asked twice when encrypt root partition on arm and x86_64

SLE 15 349.1 x86¶

osd#1269048#step/partitioning_lvm/7
osd#1269048#step/grub_test/1 password asked
osd#1269048#step/boot_encrypt/1 password asked
- bsc#1067479 - passphrase is asked twice when encrypt root partition on arm and x86_64

Subtasks 5 (0 open — 5 closed)

action #25376: [sle][functional][ppc64le][hard] test fails in grub_test - stuck in grub screen, expected encrypted password prompt (was: boots completely)

Resolved

SLindoMansilla

2017-09-18

2017-12-06

Actions

action #28507: [sle][functional][story][hard] Proposed partitions for "encrypted lvm" including encrypted boot partition

Resolved

riafarov

2017-11-28

2018-02-27

Actions

action #28510: [sle][functional][story][hard][bsc#1070139] "encrypted LVM-based" partition schema with non-encrypted boot partition

Rejected

2017-11-28

2018-01-30

Actions

action #28791: [sle][functional][medium] test fails in boot_encrypt - Workaround for crypt-password-prompt on serial console

Resolved

2017-12-04

2018-01-16

Actions

action #27829: [sle][functional][medium]test fails in reboot_gnome - grub2 needs unlock

Resolved

okurz

2017-11-17

2018-02-13

Actions

Copy link

Updated by SLindoMansilla over 6 years ago

Subject changed from [sle][functional][epic] crypt lvm for SLE 15 to [sle][functional][epic] crypt lvm for SLE 12-SP3, SLE 12-SP4 and SLE 15
Description updated (diff)

Actions

Copy link

Updated by okurz over 6 years ago

Category set to Bugs in existing tests

let's handle this as "bugs in existing tests". This is a nice collection ticket but what are the ACs?

Actions

Copy link

Updated by SLindoMansilla over 6 years ago

Description updated (diff)

ac's added

Actions

Copy link

Updated by okurz over 6 years ago

Status changed from New to Feedback
Assignee set to SLindoMansilla
Target version set to Milestone 13

@SLindoMansilla because you are the reporter of the bug please track the status and tell us in this progress ticket when it's done and we have the effect in the build. Then we can schedule it for a specific sprint. If the bug is still not resolved at the end of the milestone we should revisit and discuss how to continue.

Actions

Copy link