When configuring an interface with a static address, anaconda imposes unnecessary requirments. Given the following two lines in a kickstart file, network --onboot yes --device eth0 --noipv6 --bootproto dhcp --hostname myhost network --onboot yes --device eth1 --noipv6 --bootproto static --ip 192.168.0.254 --netmask 255.255.255.0 anaconda chokes because --gateway and --nameserver arguments are not present. This is unreasonable because, as a secondary interface, eth1 does not need and should not have an assigned gateway, and because nameservers are provided for the entire system by the DHCP response on the eth0 interface. anaconda should provide some way to specify that the user does not want to assign a gateway or nameserver to an interface. Perhaps "--gateway=none" or "--nameserver=none".
*** Bug 1117640 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.
I've reproduced this in F22. The kickstart is configured as such: # Network information network --bootproto=dhcp --device=eth0 --ipv6=auto --activate network --bootproto=static --device=eth1 --ip=172.16.1.3 --netmask=255.255.255.0 --onboot=on --nodefroute network --hostname=localhost.localdomain I was able to work around it by adding --gateway=0.0.0.0 to the line. If this is the intended behavior, it should be better documented. Just using --nodefroute, as would seem to be sufficient, was not.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.