Bug 166091 - If a FC install is found, you are never given a chance to re-install
Summary: If a FC install is found, you are never given a chance to re-install
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: ia64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: fedora-ia64
TreeView+ depends on / blocked
 
Reported: 2005-08-16 20:36 UTC by erikj
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-12-13 19:25:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description erikj 2005-08-16 20:36:40 UTC
This was observed on ia64 with fedora core development.
In our mirror, the kernel was at kernel-2.6.12-1.1485_FC5.ia64.rpm
and anaconda was at anaconda-10.3.0.7-1.ia64.rpm.

I had a previous install of Fedora Core development on the machine.  I wished
to wipe it out and start over again with a new one.  I even marked the FC
related filesystems for "re-format" in disk druid.

Other non-Fedora/Redhat operating systems were present on the machine.

I was never given the menu where you can select "workstation, server, custom, 
etc" like I was before.  Instead, it just started installing stuff even though
it formatted the filesystems fresh.

When I booted in to a different OS on the machine and re-created the 
filesystems that previously held FC Development, rebooted, and tried the
install again... Then I was given the chioce to install workstaiton, server,
custom, etc. 

Therefore, it appears that if the FC installer sees that there is an FC 
already on the disk, it seems to skip allowing you to select what type of 
system you'd like.

Please be advised that this could be related to bug 166088

Comment 1 Chris Lumens 2005-10-12 18:15:14 UTC
Yes, this is most likely related.  We currently have the upgrade and "pick your
installation type" disabled.

Comment 2 Chris Lumens 2005-12-13 19:25:19 UTC
Update screen is back and should be working.


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