Bug 1085310
| Summary: | [CSB] anaconda doesn't initialize network without specifying network --device option when installing from kickstart on media | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Daniel Mach <dmach> |
| Component: | anaconda | Assignee: | Radek Vykydal <rvykydal> |
| Status: | CLOSED ERRATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | mbanas, mkovarik, rvykydal |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | anaconda-21.48.22.43-1 | Doc Type: | Known Issue |
| Doc Text: |
Network devices are not automatically enabled during installation unless the installation method requires network connectivity. As a consequence, a traceback error can occur during Kickstart installation due to inactive network devices. To work around this problem, set the ksdevice=link option on boot or add the --device=link option to the ks.cfg file to enable network devices with active links during Kickstart installation.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 09:46:38 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1186677 | ||
The warning message is wrong. By default anaconda does not activate any network device if it is not needed in initramfs. Adding --device=link to kickstart network command, ie: network --bootproto=dhcp --activate --device=link should work. We might be able to fix this bug by assuming ksdevice=link, but we need to be careful here and check that this assumption doesn't introduce regressions breaking some other scenarios. Also, we'll need to look for a device with link in dracut environment in parse-kickstart. I posted a patch for review. New behaviour: 1) fixed --device=link option 2) if --device is missing a) use ksdevice boot option if set b) assume --device=link if ksdevice is not set 3) keep possibility to configure only hostname without configuring a device, ie for network --hostname=blah a) if ksdevice is present, configure the device with defaults b) if not, just set the hostname, ie we don't assume --device=link in this case *** Bug 1253621 has been marked as a duplicate of this bug. *** Proposed patches - https://github.com/rhinstaller/anaconda/pull/298 Yes, installation with updates.devicelink.img activates network. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-2284.html |
Problem: anaconda doesn't initialize network when installing from kickstart on media Reproducer: Place a kickstart file (ks.cfg) on installation media. Use following network settings: network --bootproto=dhcp --activate Add following to isolinux.cfg: ks=hd:LABEL=<LABEL>:/ks.cfg Result: no network available Expected : network available More details: parse-anaconda-net.sh : link) warn "'ksdevice=link' does nothing (it's the default behavior)" ^^ this is obviously *not* a default. Setting ksdevice=link activates network on boot.