Bug 426446 - install, upgrade and update fail
Summary: install, upgrade and update fail
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 8
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-12-21 02:50 UTC by jim bodkins
Modified: 2008-01-24 15:59 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-01-24 15:59:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description jim bodkins 2007-12-21 02:50:25 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11

Description of problem:
Fedora 8 DVD was verified. A 'large' install was tried twice, both times corrupted packages were found on the DVD which resulted in termination of install. A 'minimal' install succeeded, but the update process destroyed the filesystems. (/usr went missing) CentOS 5 was installed after this with no issues.

A different system running Fedora 6 was (attempt) upgraded. The process hung at checking dependencies for packages selected for installation.

Has this been tested? This happened in front of a business who was considering moving to Fedora. They have decided not to. This version doesnt appear to be ready for prime time. I would suspect the media, expect it passed verification.

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


How reproducible:
Always


Steps to Reproduce:
1.I selected 'everything' and installed. It failed.
2. I allowed auto update on a new install, that failed.
3. I booted on the DVD (Fedora 6 system) and selected upgrade - that hung.

Actual Results:
See description

Expected Results:
Installs, updates and upgrades.

Additional info:
I'm sure this works for some. Sadly, I fell off the porch.

Comment 1 Chris Lumens 2008-01-24 15:59:42 UTC
Yes of course we tested it.  We test this a lot.  However different people have
different hardware which could have different problems, so we must rely on the
community for testing as well to make sure we get good enough coverage.

Without extra information (like the /tmp/anaconda.log or /tmp/syslog) from your
system, we will most likely not be able to debug what's going on.  We don't have
enough information here to do anything.


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