Bug 1039261 - Partitioning information in anaconda-ks.cfg is incorrect when using LVM encryption with custom partitioning
Summary: Partitioning information in anaconda-ks.cfg is incorrect when using LVM encry...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-07 10:46 UTC by Alexey Torkhov
Modified: 2015-06-29 13:25 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 13:25:45 UTC
Type: Bug


Attachments (Terms of Use)
anaconda-ks.cfg (1.51 KB, text/plain)
2013-12-07 10:46 UTC, Alexey Torkhov
no flags Details

Description Alexey Torkhov 2013-12-07 10:46:43 UTC
Created attachment 833864 [details]
anaconda-ks.cfg

Description of problem:

When using custom partitioning with LVM encryption partitioning information in kickstart is looks like:

# Disk partitioning information
part luks --fstype="luks" --ondisk=vda --size=7691
part /boot --fstype="ext4" --ondisk=vda --size=500
volgroup fedora --pesize=4096 pv.37
logvol /  --fstype="ext4" --grow --maxsize=51200 --size=1024 --name=root --vgname=fedora
logvol swap  --fstype="swap" --size=819 --name=swap --vgname=fedora

Seems there is no any kind of connection between luks and PV. It is not possible to replicate installation using such kickstart.

Full kickstart is in attachment.

Version-Release number of selected component (if applicable):
anaconda-20.25.14-1.fc20.x86_64

Comment 1 Fedora Blocker Bugs Application 2013-12-07 10:48:17 UTC
Proposed as a Blocker for 20-final by Fedora user atorkhov using the blocker tracking app because:

 The installer must be able to complete a scripted installation which duplicates the default interactive installation as closely as possible.

Comment 2 Alexey Torkhov 2013-12-07 11:04:39 UTC
There is no encryption passphrase in ks too (should it be there?).

Comment 3 Alexey Torkhov 2013-12-07 21:01:08 UTC
Custom partitioning does not looks like "default" installation. Just nice to have feature. Removing blocker proposition.

Comment 4 Chris Lumens 2014-03-13 18:53:23 UTC
No, encryption passphrases should always be removed as there are some security concerns over having passphrases in readable files, even if they are only readable by root.

Comment 5 Fedora End Of Life 2015-05-29 09:56:26 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Fedora End Of Life 2015-06-29 13:25:45 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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