Bug 108097
Summary: | install exited abnormally during 7.1 upgrade | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux Beta | Reporter: | Mike McLean <mikem> |
Component: | anaconda | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED WORKSFORME | QA Contact: | Mike McLean <mikem> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | beta2 | CC: | webmaster |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-04 13:58:40 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike McLean
2003-10-27 17:19:27 UTC
Reproducible? 7.0 minimal upgrade sez "error reading information on service linuxconf: No such file or directory" right before it dies, but I'm not sure if the message has anything to do with the crash. Hmmm, did 7.1 minimal + linuxconf install and it's upgrading fine now :/ This problem affects 7.0, 7.1, and 7.2 installs. The installer exits abnormally during the "Preparing to install" phase. upgrade from minimal installs seem to be ok. upgrades from everything installs fail. I ran a testcase upgrading from 7.2 minimal+linuxconf -- it failed. Confirmed that manually upgrading from 7.2 min+linuxconf also fails I think the message "error reading information on service linuxconf: No such file or directory" only appears when you try the upgrade again after it has failed. Presumably anaconda manages to remove linuxconf before it dies. Almost certainly the linuxconf removal code... workaround is to remove linuxconf manually by hand beforehand. As I said last week, though, I'm not convinced this is going to be a huge problem -- upgrades from 7.x to Fedora aren't what I expect to be common. Hmm, anaconda doesn't quite manage to remove linuxconf. All the files are removed, but the entry remains in the rpm database. I ran into this same problem intalling RHEL AS 2.1 for i386 update 2 on a Compaq Proliant (w/ 3 disk raid). Repartitioned/formatted, via anaconda -- so it does not appear to be an upgrade issue. Tried ide=nodma -- no luck. <Ctrl>+<Alt>+<F4> shows a whole bunch of cdrom_decode_status/SeekComplete errors. Red Hat 7.2, 7.3, and 8.0 all installed and ran on this precise hardware configuration w/o error . . . Does this still happen? Closing due to inactivity. Please reopen this bug if you have further information to add to the report. |