Bug 62210 - Anaconda gets time to completion wrong
Summary: Anaconda gets time to completion wrong
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: skipjack-beta1
Hardware: i386 Linux
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2002-03-28 14:16 UTC by Jeremy Sanders
Modified: 2007-04-18 16:41 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-03-28 14:17:00 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Jeremy Sanders 2002-03-28 14:16:55 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020314

Description of problem:
When installing redhat, the time bar is consistently wrong. We install from NFS,
and it typically starts off (after a few packages) at half the time it actually
takes. The time gradually increases through the installation. This worked for
the anaconda that was shipped for RedHat 6.1.

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

How reproducible:

Steps to Reproduce:
1. Install RH from NFS (Skipjack, 7.1, 7.2)
2. Watch time bar

Additional info:

Comment 1 Michael Fulbright 2002-03-28 20:09:15 UTC
The time is only an estimate and is roughly correct once enough packages have
been installed to smooth out differnces between large and small package install

Comment 2 Jeremy Sanders 2002-03-28 20:41:24 UTC
I think there is still a bug in the time estimation code. The time doesn't
settle down after a few packages, but just continually increases. This didn't
happen with RedHat 6. I'll have to do some timing tests to be sure.

Comment 3 Bill Crawford 2002-04-03 03:35:20 UTC
Similar experience here with FTP install on a laptop ... it consistently starts
out with about half the right amount and steadily builds up.  It is an issue;
you get excited, and then disappointed.  If it started off showing a larger
value, you think "I'll go make a cup of tea" (or fetch a Molson, if your name's
Mike Harris :o)

Perhaps something could be done to alleviate this?  I remember many versions
back a hard-drive install consistently *over*-estimated to begin with.

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