Bug 1477614 - [RFE] You should be able to manually unlock a luks device and then do the partitioning from the gui installer
Summary: [RFE] You should be able to manually unlock a luks device and then do the par...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: python-blivet
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Vojtech Trefny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-02 13:26 UTC by Peter Gervase
Modified: 2023-04-26 12:05 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Peter Gervase 2017-08-02 13:26:09 UTC
Description of problem:
As mentioned in bug 1477351, I have some issues with the installer and my vg. For troubleshooting that, I tried manually unlocking the luks device, mounting, ... making sure the volgroup was OK. After that, I went into the graphical installer and tried to configure partitioning. When I did that, I again had to enter the luks password for my encrypted drive. However, when I entered the password, I got an error, "Failed to activate device: Device or resource busy"

The installer should see that the encrypted device has already been unlocked and then not prompt you for the password to unlock it. 

Version-Release number of selected component (if applicable):
rawhide, netinstall iso from 2017-Jul-31 05:53:01 

How reproducible:
100%

Steps to Reproduce:
1. Have an encrypted drive
2. Boot up from an iso to install
3. control + alternate + f3 to get to a console
4. manually unlock your encrypted drive
5. mount one of the drives from there
6. Go back into the installer
7. Try to configure partitioning.

Actual results:
It will error after you enter the luks password in the graphical installer.

Expected results:
The installer should see that the encrypted drive has already been unlocked.

Additional info:

Comment 1 Jiri Konecny 2017-08-03 10:04:25 UTC
I guess this needs to be changed in blivet library. I guess they could look if the device is already unlocked and then ignore this unlocking attempt from Anaconda.

Comment 2 Ivan Molodetskikh 2020-02-19 09:39:34 UTC
Installing F31 and facing a similar issue: I had my LUKS unlocked, and Blivet was seeing it fine, but upon clicking Done it complained that "The existing unlocked LUKS device cannot be used for the installation without an encryption key specified for this device. Please, rescan the storage". This does make sense, however I found no way to enter the key or "rescan the storage", so I had to quit the installer altogether, manually close LUKS, and restart the installation process for it to finally work.

Comment 3 Vendula Poncova 2020-02-21 12:01:58 UTC
(In reply to Ivan Molodetskikh from comment #2)
> Installing F31 and facing a similar issue: I had my LUKS unlocked, and
> Blivet was seeing it fine, but upon clicking Done it complained that "The
> existing unlocked LUKS device cannot be used for the installation without an
> encryption key specified for this device. Please, rescan the storage". This
> does make sense, however I found no way to enter the key or "rescan the
> storage", so I had to quit the installer altogether, manually close LUKS,
> and restart the installation process for it to finally work.

Hi, you can rescan the storage by clicking at the "Refresh..." link at the bottom of the Installation Destination screen or click at the "Reload storage configuration from disk" button next to the buttons for adding or removing a mount point at the Manual Partitioning screen. After the rescan, you should be able to unlock the device in the Manual Partitioning screen.

Comment 4 Fedora Admin user for bugzilla script actions 2023-04-26 00:29:47 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Fedora Admin user for bugzilla script actions 2023-04-26 12:05:45 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.


Note You need to log in before you can comment on or make changes to this bug.