| Summary: | Anaconda fails to download kickstart file when specified using "ks=http://" or "ks=nfs:" on UV systems. | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Tony Ernst <tee> | ||||||||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 6.2 | CC: | ebenes, gbeshers, rja | ||||||||||
| Target Milestone: | rc | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-07-10 15:35: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: | |||||||||||
| Attachments: |
|
||||||||||||
|
Description
Tony Ernst
2012-02-09 23:07:07 UTC
Created attachment 560730 [details]
Log files from /tmp
Here are all of the log files from /tmp after the error occurs.
Please attach the logs as individual plain/text attachments. This makes it alot easier to evaluate them, and allows bugzilla to search them. Created attachment 560900 [details]
/tmp/anaconda.log
Created attachment 560901 [details]
/tmp/syslog
I've reattached all of the files from /tmp. Please note that there was also an empty zero-length ks.cfg in /tmp. In the syslog, note the relatively short amount of time between when ethX comes up and when it attempts to fetch the kickstart file. I wonder if there's some sort of timing problem here where the interface isn't really quite ready yet. Your test from the shell works because enough time has elapsed. Hmm. You're right. After the error, if I wait a minute and try again, it works. So when it says "Waiting for NetworkManager to configure eth0", it must not really be waiting until the interface is up. Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. No, the waiting for NetworkManager message is waiting for NetworkManager to tell us it's done. "Done" is defined by NetworkManager in that sense, which may or may not translate to "wait until the network link is up and traffic is flowing". A workaround that may work in your case is the linksleep= parameter. Add linksleep=5 or something like that to your installer boot command line and see if that works. I'm no longer set up to test this, but I'll make a note of the linksleep= parameter in case it ever comes up again. I've lowered the Severity, since there is an easy workaround (waiting a few seconds and retrying). Thanks. This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. devel_ack- per comment #11. Development Management has reviewed and declined this request. You may appeal this decision by reopening this request. This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4. |