Bug 894772

Summary: Cannot install to pre-exists /boot partition, complaining disklabel issue
Product: [Fedora] Fedora Reporter: Koala Yeung <koalay>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, g.kaviyarasu, jonathan, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 14:47:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
storage.log
none
program.log none

Description Koala Yeung 2013-01-13 18:32:29 UTC
Description of problem:


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


How reproducible:
Install Fedora 18 RC4 (amd64) install DVD with the new installer.

Steps to Reproduce:
1. Partition a harddisk with ext4 partition (as boot) and whatever other partition layout (/, /home, etc). Fully use the harddisk and leave no space for extra partitions.
2. Boot the system with Fedora 18 RC4 (amd64) install DVD.
3. Select to customize partition table yourself.
4. Specify to use the /boot partition as /boot
5. Apply the partition
  
Actual results:
It denies me from installing. Complaining: "must have one of the following disklabel types: gpt"

Expected results:
Install normally.

Additional info:

Comment 1 Brian Lane 2013-01-15 01:01:33 UTC
Please switch to tty2 (ctrl-alt-f2) and attach the logs from /tmp/*log to this bug as individual text/plain files.

Comment 2 Koala Yeung 2013-01-16 06:44:43 UTC
Created attachment 679387 [details]
anaconda.log

Comment 3 Koala Yeung 2013-01-16 06:45:38 UTC
Created attachment 679388 [details]
storage.log

Comment 4 Koala Yeung 2013-01-16 06:46:19 UTC
Created attachment 679389 [details]
program.log

Comment 5 Koala Yeung 2013-01-16 06:50:21 UTC
These are the related logs.
I'm not uploading X.log, ifcfg.log and packaging.log because they seems irrelevant.

Comment 6 Fedora End Of Life 2013-12-21 10:21:40 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 Fedora End Of Life 2014-02-05 14:47:56 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.