Bug 1635798 - No way to skip "You must create a new file system on the root device"
Summary: No way to skip "You must create a new file system on the root device"
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 28
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-03 17:05 UTC by lukasstraub2
Modified: 2019-05-28 23:03 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 23:03:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
The Kickstart file (5.16 KB, text/plain)
2018-10-03 18:00 UTC, lukasstraub2
no flags Details

Description lukasstraub2 2018-10-03 17:05:04 UTC
Description of problem:
Hello Everyone,
I want to install Fedora using a Kickstart file. However, creating Partitions and Filesystems is too limited using the standard commands. So I create everything using a %pre Script (attached). But then anaconda will not let me continue with the following Message: "You must create a new file system on the root device".

Version-Release number of selected component (if applicable): anaconda 28.22.10-1.fc28

How reproducible:

Start the attached kickstart using a fedora workstation 28 install CD/USB-Drive on a Machine with a *single* disk (the Part for multiple Disks is not yet handeled on the Script side).

Actual results:
Anaconda shows a "You must create a new file system on the root device" Error, which is unable to skip. 

Expected results:
Kickstart installation should run as always.

Additional info:
IMHO this Message should be just a warning that should be skip-able interactively *and* in the Kickstart file (so it can run unattended).

Comment 1 lukasstraub2 2018-10-03 18:00:09 UTC
Created attachment 1490194 [details]
The Kickstart file

Comment 2 lukasstraub2 2018-10-25 16:46:41 UTC
Hello Everyone,
Any Comments on this?

Regards,
Lukas Straub

Comment 3 Jiri Konecny 2018-10-26 12:26:20 UTC
Hello,

The problem is this line in your kickstart file:

logvol / --noformat --useexisting


As said in the error message we are not supporting installation on the un-formatted / partition. The result wouldn't work most of the times.

Why do you want to use root partition without formatting it?

Comment 4 lukasstraub2 2018-10-26 15:32:32 UTC
Because I already manually format it in the %pre-script:

mkfs.btrfs -L root -d dup -m dup /dev/rootvg/root

I do it this way because there is no way to pass more than one Option to mkfs using --mkfsoptions.

But generally I want to be able to manually Create the Storage configuration because there's at least another case that is not possible with the anaconda commands. (md raid10 with less than 4 Drives and/or custom Layout )

Comment 5 Vendula Poncova 2018-10-29 11:16:54 UTC
Hi,

based on the pykickstart documentation [1], it should be possible to pass more that one option to mkfs:

--mkfsoptions MKFSOPTS

Specifies additional parameters to be passed to the program that makes a filesystem on this partition. No processing is done on the list of arguments, so they must be supplied in a format that can be passed directly to the mkfs program. This means multiple options should be comma-separated or surrounded by double quotes, depending on the filesystem.

Also, you might be interested in the kickstart command mount [2]. However, you will still need to reformat root.

[1] https://pykickstart.readthedocs.io/en/latest/commands.html#logvol
[2] https://pykickstart.readthedocs.io/en/latest/commands.html#mount

Comment 6 Ben Cotton 2019-05-02 20:33:16 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 7 Ben Cotton 2019-05-28 23:03:43 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.