Bug 1258187 - Anaconda creates un-bootable partition scheme for Atomic
Anaconda creates un-bootable partition scheme for Atomic
Status: CLOSED EOL
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
22
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-29 22:42 EDT by Victor Costan
Modified: 2016-07-19 13:43 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-07-19 13:43:24 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Partition scheme created by anaconda (366.95 KB, image/png)
2015-08-29 22:42 EDT, Victor Costan
no flags Details

  None (edit)
Description Victor Costan 2015-08-29 22:42:19 EDT
Created attachment 1068381 [details]
Partition scheme created by anaconda

Description of problem:
A partition scheme produced by Anaconda results in an un-bootable Atomic system.

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


How reproducible:
This reproduces in the official Atomic 22 ISO, the nightly 22 ISO, the 23 Alpha ISO, and the 23 Beta TC1 ISO.

Steps to Reproduce:
0. The easiest way to reproduce this is to build a new VM. You'll need a large hard disk to experience the bug. I don't know how large it needs to be, but 50GB is too small and 128GB is enough.
1. Start an installation using an Atomic ISO, such as https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud_Atomic/x86_64/iso/Fedora-Cloud_Atomic-x86_64-22.iso
2. Select System > Installation Destination, then Other Storage Options > I will configure partitioning, then click the Done button.
3. Under New Fedora 22 Installation, click the "Click here to create them automatically" link.


Actual results:
The recommended partitioning scheme has a /home partition, as shown in the attached screenshot. That will prevent the system from booting.

Expected results:
The recommended partitioning scheme should be something that the OS can boot with. Ideally, it should mirror what the Automated partitioning option would produce, namely a small root partition and a docker-pool.

Additional info:
I think that the underlying problem is that OSTree expects to be able to hardlink everything under /, including /home. After reading how Atomic works, having a separate /home partition strikes me as very un-intuitive.

If I just go for Automated partitioning instead of the list of steps I provided, Anaconda produces a good scheme. So far, I have preferred the steps I provided because they allow me to review the partition table changes before they are committed to the disk.
Comment 1 Fedora End Of Life 2016-07-19 13:43:24 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.