Since Fedora-25-20160904.n.0 , one of our openQA tests has failed on every compose. That test uses a kickstart that looks like this:

install
cdrom
bootloader --location=mbr
network --device=link --activate --bootproto=static --ip=10.0.2.101 --netmask=255.255.255.0 --gateway=10.0.2.2 --hostname=client001.domain.local --nameserver=10.0.2.100
lang en_US.UTF-8
keyboard us
timezone --utc America/New_York
clearpart --all
autopart
%packages
@^server-product-environment
%end
rootpw anaconda
reboot
realm join --one-time-password=monkeys ipa001.domain.local

The kickstart is loaded from a hard disk (it is not retrieved over the network). The network it's on has no DHCP server. When the installed system boots, it has no network connectivity. With Fedora-25-20160903.n.0 and earlier, this worked fine.

I reproduced the issue locally with a similar kickstart, slightly tweaked for my local network settings and with a smaller package set to save install time - https://www.happyassassin.net/temp/static.ks .

If I load that kickstart over the network - i.e. inst.ks=https://www.happyassassin.net/temp/static.ks - I don't hit the bug. The installed system does use the specified static network configuration (so with my modified kickstart, it comes up with IP 192.168.1.105 , which is not in my DHCP server's range so I know it's not just getting it by luck).

However, if I load the kickstart from a hard disk attached to the VM, I *can* reproduce the bug. The installed system does not use the static configuration specified in the kickstart. In my case the connection comes up via DHCP, because I have a DHCP server on my network, but the bug is really the same - the configuration in the kickstart is not applied.

In the installed system, there is no /etc/sysconfig/network-scripts/ifcfg-(interface) file at all - there is only ifcfg-lo . The string '192.168.1.105' does not appear in any file in the whole of /etc. /var/log/anaconda/ifcfg.log does not show the static config values in its 'all settings' list.

When I load the kickstart over the network instead of from a hard disk, there *is* a /etc/sysconfig/network-scripts/ifcfg-ens3 in the installed system, with the appropriate config values, and the comment "# Generated by parse-kickstart" . /var/log/anaconda/ifcfg.log *does* show the static config values in its 'all settings' list.

I'm assigning this to NetworkManager because anaconda did not change between Fedora-25-20160903.n.0 and Fedora-25-20160904.n.0 , but NetworkManager did - it went from 1.4.0-0.5.git20160621.072358da.fc25 to 1.4.0-2.fc25 . There may well be some kind of NM<->anaconda interaction involved, though.