Bug 1420553 - Allow /boot on btrfs when not installing bootloader
Summary: Allow /boot on btrfs when not installing bootloader
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 26
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-02-08 23:54 UTC by Manu
Modified: 2018-05-29 11:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-05-29 11:21:59 UTC
Type: Bug

Attachments (Terms of Use)

Description Manu 2017-02-08 23:54:45 UTC
Description of problem:

Anaconda produces an error message and refuses to continue installation when /boot is on btrfs. This problem is related to grubby.
btrfs users often boot with something like rEFInd, so they select to skip installation of bootloader when installing. When this selection is made, it would be good if Anaconda would graciously allow installation of /boot wherever the user selects.

Version-Release number of selected component (if applicable):

F26 alpha

How reproducible:


Steps to Reproduce:
1. In advanced options, choose no-boot-loader
2. Assign /boot to install on btrfs
3. Try and continue installation, notice complains that /boot is on btrfs

Actual results:

Anaconda complains that /boot is on btrfs

Expected results:

Anaconda allows /boot on btrfs if user selected no bootloader.

Additional info:

Helps to have rEFInd installed, or the machine can't boot.

Comment 1 Fedora End Of Life 2017-02-28 11:13:38 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 2 Fedora End Of Life 2018-05-03 08:45:56 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 3 Fedora End Of Life 2018-05-29 11:21:59 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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

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.