View Issue Details

IDProjectCategoryView StatusLast Update
0017012CentOS-8cryptsetuppublic2020-02-19 18:34
Reportermayday 
PrioritynormalSeveritycrashReproducibilityalways
Status newResolutionopen 
Product Version8.1.1911 
Target VersionFixed in Version 
Summary0017012: Centos 8.1 Fails to install/unlock a pre-encrypted luks disc with LUKSError: Failed to activate device: Operation not p
DescriptionI'm trying to migrate an double layer full disc encryption workflow from Centos 7 to Centos 8.
This type of installation works on Centos 6, Centos 7 but crashes on Centos 8.

The steps to reproduce are below and normally there are no issues.
This type of installation work very well with https://github.com/gsauthof/dracut-sshd and provides a fully secure full disc encryption with two encryption layers.

instillation fails with blivet.errors.LUKSError: Failed to activate device: Operation not permitted
Steps To ReproduceStart with a blank system and one disc:
Create two partitions boot 900M, root 30G

Start Centos 8 Installation

Switch to Console alt+f2

- Create First Encrypted Layer
cryptsetup luksFormat -c aes-xts-plain64 /dev/sda2 --force-password
set lvl1 password to 1
cryptsetup luksOpen /dev/sda2 luks1

- Create Second encrypted layer
cryptsetup luksFormat -c twofish-xts-plain64 /dev/mapper/luks1 --force-password
set lvl2 password to 2
cryptsetup luksOpen /dev/mapper/luks1 luks2

- Create pv/vg/lvm
pvcreate /dev/mapper/luks2
vgcreate vg /dev/mapper/luks2
lvcreate -n root -l100%FREE vg

Restart VM/Server
After restart continue setup

Go to installation destination Choose Custom Storage Configuration, click done
Click the triangle next to unknown.
Select the Encrypted LUKS Disc input the pass and click Unlock

Installation will crash at this point. with error

blivet.errors.LUKSError: Failed to activate device: Operation not permitted



TagsNo tags attached.

Activities

mayday

mayday

2020-02-19 18:34

reporter   ~0036354

Do i need to provide more information or data to have this bug checked out?

Issue History

Date Modified Username Field Change
2020-02-06 05:44 mayday New Issue
2020-02-19 18:34 mayday Note Added: 0036354