Bug 971269

Version 2 should work but only if you specify --device (or ksdevice boot argument but this may be dropped in future). Not quite sure this is the cause of your case, I'd need to see logs.

Please attach
/tmp/anaconda.log,
/tmp/syslog,
/tmp/ifcfg.log from installer

or
/var/log/anaconda/anaconda.ifcfg.log
/var/log/anaconda/syslog
/var/log/anaconda/anaconda.log
from installed system.

Created attachment 757675 [details]
anaconda.log

Created attachment 757676 [details]
Requested log 2

Created attachment 757677 [details]
Syslog

(In reply to Radek Vykydal from comment #1)
> Version 2 should work but only if you specify --device (or ksdevice boot
> argument but this may be dropped in future). Not quite sure this is the
> cause of your case, I'd need to see logs.

The log says: unspecified network --device in kickstart, using em1 (first active device).

This is what I expect. If --device was mandatory it would be impossible to write a generic kickstart file, as nowadays you can't predict how Fedora names it's NICs.

The message comes from anaconda whereas the kickstart file is processed (ifcfg file created) in initramfs/dracut part of installer where we currently really don't support missing --device specification.

This bug is still present in rawhide:

network --onboot=yes --activate --bootproto=static --ip=212.115.199.60 --netmask=255.255.255.248 --gateway=212.115.199.57 --ipv6=2001:1af8:fe00:847f::4/64 --ipv6gateway=2001:1af8:fe00:847f::1 --nameserver=212.115.199.57,2001:1af8:fe00:847f::1
network --hostname=testsys.digifarma.nl

Becomes:
19:08:39,149 DEBUG ifcfg: content of files (network initialization):
19:08:39,149 DEBUG ifcfg: /etc/sysconfig/network-scripts/ifcfg-p2p1:
19:08:39,149 DEBUG ifcfg:   # Generated by dracut initrd
19:08:39,149 DEBUG ifcfg:   DEVICE="p2p1"
19:08:39,149 DEBUG ifcfg:   ONBOOT=yes
19:08:39,149 DEBUG ifcfg:   NETBOOT=yes
19:08:39,149 DEBUG ifcfg:   UUID="0b891551-69b1-4d8b-ae32-5348daf02cad"
19:08:39,149 DEBUG ifcfg:   BOOTPROTO=none
19:08:39,149 DEBUG ifcfg:   IPADDR="212.115.199.60"
19:08:39,150 DEBUG ifcfg:   NETMASK="255.255.255.248"
19:08:39,150 DEBUG ifcfg:   GATEWAY="212.115.199.57"
19:08:39,150 DEBUG ifcfg:   HWADDR="d8:50:e6:4e:6e:5f"
19:08:39,150 DEBUG ifcfg:   TYPE=Ethernet
19:08:39,150 DEBUG ifcfg:   NAME="p2p1"
19:08:39,150 DEBUG ifcfg:   DNS1="212.115.199.57"
19:08:39,150 DEBUG ifcfg:   DNS2="2001:1af8:fe00:847f::1"
19:08:39,150 DEBUG ifcfg:   DNS3="212.115.199.57"
19:08:39,157 DEBUG ifcfg: all settings: [{'802-3-ethernet': {'s390-options': {}, 'mac-address': [216, 80, 230, 78, 110, 95]}, 'connection': {'timestamp': 1403032114L, 'interface-name': 'p2p1', 'type': '802-3-ethernet', 'id': 'p2p1', 'uuid': '0b891551-69b1-4d8b-ae32-5348daf02cad'}, 'ipv4': {'routes': [], 'address-labels': [''], 'addresses': [[1019704276L, 29L, 969372628L]], 'dns': [969372628L], 'method': 'manual'}, 'ipv6': {'routes': [], 'addresses': [], 'dns': [], 'method': 'ignore'}}]
19:08:39,245 DEBUG ifcfg: IfcfFile.read /etc/sysconfig/network-scripts/ifcfg-p2p1
19:08:39,246 DEBUG ifcfg: IfcfFile.read /etc/sysconfig/network-scripts/ifcfg-p2p1
19:08:39,247 DEBUG ifcfg: IfcfFile.read /etc/sysconfig/network-scripts/ifcfg-p2p1

Looks like anaconda handles IPv4 difrent from IPv6.
IPv4 does not need device, where as IPv6 seems to need this.

This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

In 24_Alpha-1.7 this bug is still present.

(In reply to A.J. Werkman from comment #9)
> In 24_Alpha-1.7 this bug is still present.

I am not able to reproduce with 24_Alpha-1.7. Could you please attach installation logs?
/tmp/anaconda.log, /tmp/ifcfg.log, /tmp/syslog

This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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 '24'.

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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days