Project

General

Profile

Actions
Copy link

action #65909

closed

[functional][y] Test ENV_ACTIVATE_LUKS boot option

Added by riafarov over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
oorlov
Category:
New test
Target version:
QA (public) - future
Start date:
2020-04-21
Due date:
2020-07-14
% Done:

0%

Estimated time:
5.00 h
Difficulty:

Description

Initially filed as a bug by customer who had to enter password 96 times for encrypted partitions.

See https://trello.com/c/iao6hMQb/1741-2-sles15-sp2-p1-1162545-ses6-upgrade-finds-encrypted-disks-asks-for-password-96-times
PR with changes: https://github.com/yast/yast-storage-ng/pull/1078/files

https://en.opensuse.org/SDB:Linuxrc is also updated.

Trello card content copy:
https://bugzilla.suse.com/show_bug.cgi?id=1162545

Find a way to skip activation of (all?) encrypted devices during probing that can be reasonably implemented on time for SP2. Likely an environment variable.

Take AutoYaST into account.

Let's implement the most simple fix: an ENV variable to disable activation of encrypted devices during probing.

Review

YaST understands the environment variable YAST_ACTIVATE_LUKS. With YAST_ACTIVATE_LUKS=0 the activation of luks can be disabled.

AutoYaST should not be affected by the change. AutoYaST tries all password in the profile without user interaction.

Pain Points

  • Apparently different rubocop rules in SP1 and SP2.

Scope is 64bit

Acceptance criteria

  1. Installation with YAST_ACTIVATE_LUKS=0 boot option is tested
  2. Cancellation of the encrypted partitions activation is validated (e.g. by successful partitioning of that disk)
Actions
Copy link
 #1

Updated by riafarov over 4 years ago

  • Due date set to 2020-07-14
Actions
Copy link
 #2

Updated by riafarov over 4 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Estimated time set to 5.00 h
Actions
Copy link
 #3

Updated by oorlov over 4 years ago

  • Status changed from Workable to In Progress
  • Assignee set to oorlov
Actions
Copy link
 #4

Updated by oorlov over 4 years ago

  • Status changed from In Progress to Resolved

The feature tested. Covered scenarios:
Pre-condition:
Installation is performed on the system with previously encrypted drives.
Verified:

  • YAST_ACTIVATE_LUKS=0 -> Popups with the password prompts were not shown, encryption is cancelled;
  • New partitioning is performed;
  • System is installed and booted.
Actions
Copy link

Also available in: Atom PDF