Bug 49615
| Summary: | Installer | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | greg hosler <greg> |
| Component: | anaconda | Assignee: | Brent Fox <bfox> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-10-01 16:01:24 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
greg hosler
2001-07-21 17:09:55 UTC
This defect is considered SHOULD-FIX for Fairfax. the name lookup is a requirement for proper /etc/hosts configuration. It seems to me that something is amis, and you're refusing to even acknowledge that there is an issue here. Depending upon which packages, and how many packages I select, this timeout I am pointing you at will take from 10 secs, to 30 secs, to 1 minute to 4 or 5 minutes, and if you do an "everything install" it will probably take 7 to 10 minutes. This is on a P3-933, with 512MB ram, so you know there is no swapping, no thrashing issues. Also, because the delay is variable, and depends upon which packages, it is also obvious that this timeout is happening MORE THAN ONCE. While I can appreciate your assertion that "name lookup is a requirement for proper /etc/hosts configuration", I hasten to point out that if instead of giving a DNS IP number of a yet to be configured DNS server, I defaulted to Dynamic IP service (and mind you I am on a network without any DHCP server running), there is ZERO delay in the post install configuration stage, WITH EXACTLY THE SAME PACKAGE SELECTION. So don't write this off as "name lookup is a requirement" because CLEARLY IT IS NOT, proven by setting up the network w/ a NON-EXISTANT Dynamic IP service. I appreciate the fact that you wish to close bugs, but there is something amis, and you're pretending that you're not even considering the possibility. During installation, it is probably the case that there shouldn't even be any hostname lookups... And if infact there needs to be, then there ought to be some pop-up warning message that such-and-such hostname is failing to resolve properly when the lookup times out. (This will at least clue the user in that he/she has some post-boot work needing to be done). Brent please try to reproduce. What kind of install were you trying? cdrom, hard drive, network, etc? Installation notes: custom installation, from cdrom(s), to scsi hard disk (neither of which are important). The hang will vary depenging upon the selection of packages. Many network services selected, inclufdng NIS (with self as the NIS server). In network setup, "local assigned IP" is selected (as opposed to DHCP assigned), and DNS is set to self (which is to say it is not configured 'till after reboot - I run a local caching name server). I suspect that this last is important. It "feels" as though some packages are doing hostname lookups as part of their post-install, and this is timing-out. I have not identified the packages, but in multiple trys to pinpoint this, I noted that certain large selection of packages will breeze right thru, and other selections will hang for up to 8 minutes. As I recall (and I have not tried this lately), if I configure the network setup to DHCP, I do not see the hang (even though there is no DHCP server available) - this should be re-confirmed as I am no longer positive about this. I did a cdrom install with the latest tree, setting the DNS to 127.0.0.1 and didn't notice any lag at all. I don't know where the delays you are seeing are coming from. When you are noticing the lag, can you look on VC4 and see if there are any messages related to the cdrom? Any more information here? I just did an fresh install of enigma. The delay that used to be immediately after "post install configuration" and before "create boot floppy" no longer seems to be there. Perhaps this was fixed in one of the beta's / rc's since the original report. I'm satisfied that this is closed. If I see it in the next round, I'll gather more info, and open a new bugzilla. -Greg Ok. Thanks for working with us on this issue. |