Bug 165587
Summary: | kickstart fails to fetch ks.cfg from a network location without DHCP | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Noam Meltzer <tsnoam> |
Component: | pump | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | pat.lampert |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-19 20:14:48 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
Noam Meltzer
2005-08-10 16:42:54 UTC
If you have spanning tree enabled, then you also need to enable portfast. Otherwise, there is no way to programatically tell that the switch is just dropping all traffic. Doing a "sleep" like this would penalize all users who have their network set up properly with about a minute of additional time per install. Hello, I disagree with the fact that this isn't a bug. I tried using the 32bit version on my environment and there I had no problem, it worked flowlessly. Then I noticed that on the 32bit version, the loader process *do wait* until the link will be truly up. So I believe that this is a bug in the x86_64 ver. and should be fixed. Regarding the claim that this will penalize other users in about a minute of additional time, this is wrong - adding a "sleep" of 5-10 sec. is not 60 sec. and besides if it is, then it is a very small price to pay in exchange to the fact that problematic users (like me) will be able to kickstart their linux. Additionaly, we're talking about the installation procedure, which is a one time procedure - unlike the bootup of an installed OS, for example. About the "portfast" - I will check it. Noam Also set trunk off. I had spanning tree with portfast and still had problems timing out. Turned off trunking for the port and the problems went away. Hope this helps, Dan Yeah, trunking can also cause problems and, per the manufacturer, shouldn't be enabled for ports which are connected to machines (as opposed to routers) Hi, I do not agree with the claim that trunking shouldn't be enabled for machines. At some configurations it is most needed (for example - you want to double your bandwidth). Anyhow, please don't forget that this error does not exist on the x86_32bit ver. of RHEL3 but does exist on the 64bit version. Thus, it *is* a bug and must be fixed. Noam REOPENED status has been deprecated. ASSIGNED with keyword of Reopened is preferred. HP would like to submit a suggestion that Red Hat consider enhancing the network capabilities of kickstart. Increasingly, major customers of HP and Red Hat are setting up systems with multiple NICS and often use aggregate NIC bonding pairs. The use of aggregate NIC bonding requires that the ports the NICS are connected to be trunked. Because the simple network interface in kickstart is not able to emplement the final network configuration desired by customers it becomes inconvenient to use kickstart because the switch needs to be manually reconfigured after each installation. |