Bug 1117796
| Summary: | Anaconda using kickstart is not waiting for network | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Marian Csontos <mcsontos> | ||||
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 21 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, rvykydal, samuel-rhbugs, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-12-02 03:14:21 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Is there an easy workaround? I am not a systemd nor networking expert, shall one of the anaconda units "Wants" or "After" the NetworkManager-wait-online.service? Or the network-online.target? Could you please post the kickstart file you are using? Does unattended ks install work if you leave out network command from kickstart? I haven't been able to reproduce the issue yet. Modifying systemd unit dependencies could work as a workaround, though I'm not sure what exactly you need, I think I've seem some systemd doc/hints on wait-online issues. You should be able to use updates image for the workaround. This is likely a timing issue - I am running 30+ VMs on the host and it looks like dnsmasq is taking some time to find and assign an IP address. 1. I will retry with newer tree and post the KS. 2. Perhaps something to do with IPv6 and IPv4 - so I will try to install with ipv6.disable=1 on kernel cmdline. BTW, is not the network command in KS affecting only the installed system? /me wonders how is the machine getting the KS file when network is unavailable... This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Created attachment 916752 [details] anaconda logs Description of problem: anaconda 21.46-1 installer hangs on network configuration: 5) [!] Network configuration 4) [x] Installation Destination (Not connected) (Custom partitioning selected) ... Please make your choice from above ['q' to quit | 'b' to begin installation | 'r' to refresh]: anaconda.log:09:17:04,714 WARN anaconda.stdout: Not asking for VNC because we don't have a network anaconda.log:09:17:05,383 DEBUG anaconda: network: devices found ['ens3'] anaconda.log:09:17:05,644 DEBUG anaconda: network: setting real kickstart ONBOOT value for devices ['ens3'] syslog:09:17:06,235 INFO dhclient: DHCPREQUEST on ens3 to 255.255.255.255 port 67 (xid=0x15c5b195) syslog:09:17:06,044 INFO kernel:[ 45.234232] vda: unknown partition table syslog:09:17:06,113 INFO kernel:[ 45.303457] vdb: unknown partition table syslog:09:17:14,862 INFO dhclient: DHCPDISCOVER on ens3 to 255.255.255.255 port 67 interval 5 (xid=0x41f5928b) syslog:09:17:14,864 INFO dhclient: DHCPREQUEST on ens3 to 255.255.255.255 port 67 (xid=0x41f5928b) syslog:09:17:14,864 INFO dhclient: DHCPOFFER from 192.168.144.1 syslog:09:17:14,865 INFO dhclient: DHCPACK from 192.168.144.1 (xid=0x41f5928b) In the kickstart there is following network config line: network --onboot yes --device ens3 --bootproto dhcp --noipv6 Version-Release number of selected component (if applicable): anaconda 21.46-1 How reproducible: so far 2/2 Actual results: Anaconda hangs during ks install Expected results: Installation should continue after network is up Additional info: