Bug 188130 - Installer doesn't show progress of script execution
Summary: Installer doesn't show progress of script execution
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda   
(Show other bugs)
Version: 5
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Peter Jones
QA Contact:
Whiteboard: bzcl34nup
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2006-04-06 10:18 UTC by David Howells
Modified: 2008-05-06 15:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 15:45:44 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 David Howells 2006-04-06 10:18:55 UTC
I upgraded my desktop machine to FC5. Once it had installed all the files, and  
the progress bar reached the end, the installer just sat there, apparently  
doing nothing, but not offering the reboot option.  
I switched to the shell, and looked at what was going on underneath, and it  
looked like a bunch of processes were stuck in the D-state.  Attaching strace  
to the installer, however, showed that it was running various scripts - though  
no evidence of this was displayed on the installer screen.  
The installer spent about an _hour_ in this state.  Until I actually went and  
probed it, I was wondering if the installer was stuck, and when I went to the 
shell and ran ps a few times, my first impression was that the machine had 
crashed or had deadlocked in some way.  
Can we please show the script execution state in the installer window, so  
it's obvious progress is being made?

Comment 1 Jeremy Katz 2006-04-10 18:10:30 UTC
This is actually caused by the fact that we don't take into account the
"cleanup" step where the old package is removed.

Comment 2 Jacek Pliszka 2006-04-23 22:53:43 UTC
I would love to have it too ...

We have kickstart files where local configuration is done in %post scripts.

Usually it takes more than the rest of the installation itself ...

Comment 3 Red Hat Bugzilla 2007-08-21 05:23:15 UTC
User pnasrat@redhat.com's account has been closed

Comment 4 Bug Zapper 2008-04-04 02:34:52 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 5 Bug Zapper 2008-05-06 15:45:42 UTC
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

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.