Bug 1399269

Description of problem:
Installing Fedora 25 in a Xen HVM domU with a paravirtualized NIC (vif) and configuring a static IPv4 IP, route and DNS server results in these settings being ignored and DHCP used instead upon the initial reboot.

Version-Release number of selected component (if applicable):
1.4.2-1

How reproducible:
Always

Steps to reproduce:
1. Install using Fedora-Server-netinst-x86_64-25-1.3.iso (I selected "Minimal Install")
2. Configure static IPv4
3. Begin installation
4. Reboot after the installation has finished
5. The system is using DHCP instead of the manually entered IPv4 settings during setup

Actual results:
eth0 is using DHCP instead of the manually configured IPv4 settings during setup.

Expected results:
eth0 should be using the manually configured IPv4 settings during setup.

Additional info:
The file /etc/sysconfig/network-scripts/ifcfg-eth0 exists and does in fact contain the correct IPv4 information entered during the setup.

# nmcli connection
NAME                UUID                                  TYPE            DEVICE
Wired connection 1  7bac94c9-9022-384f-897b-a0314eee14b0  802-3-ethernet  eth0   (GREEN COLORED LINE)
eth0                b8e69077-a2b4-3de4-9fd7-097eda50b7e3  802-3-ethernet  --     (WHITE COLORED LINE)

# nmcli device
DEVICE  TYPE      STATE      CONNECTION
eth0    ethernet  connected  Wired connection 1 (GREEN COLORED LINE)
lo      loopback  unmanaged  --                 (BLUEISH COLORED LINE)

Workaround:
After some trial and error of reinstalling the VM a couple of times I came up with the following workaround:
1. Verify the IP address using: ip addr show eth0
Then execute these commands:
2. nmcli connection delete "Wired connection 1"
3. nmcli connection delete "Wired connection 1"
Yes, this must be executed twice. If you do it once, it will still be set to the address received via DHCP.
4. Verify the IP again using: ip addr show eth0
It should now be using the manually configured IPv4 address that was entered during setup.

After executing the above workaround, the nmcli output has changed a little bit as follows:
# nmcli connection
NAME                UUID                                  TYPE            DEVICE
eth0                b8e69077-a2b4-3de4-9fd7-097eda50b7e3  802-3-ethernet  eth0   (GREEN COLORED LINE)
Wired connection 1  7bac94c9-9022-384f-897b-a0314eee14b0  802-3-ethernet  --     (WHITE COLORED LINE)

# nmcli device
DEVICE  TYPE      STATE      CONNECTION
eth0    ethernet  connected  eth0       (GREEN COLORED LINE)
lo      loopback  unmanaged  --         (BLUEISH COLORED LINE)