Comment 14 for bug 1556241

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2016-03-21 14:34 EDT-------
Dimitri,
could the parmfile be the problem? E.g., mine looks like this:

ro locale=C cio_ignore=all,!9,!f5f0-f5f2,!eb15,!1800-19ff
s390-netdevice/choose_networktype=qeth DEBCONF_DEBUG=5
s390-netdevice/qeth/choose=0.0.f5f0-0.0.f5f1-0.0.f5f2
s390-netdevice/qeth/port=0 s390-netdevice/qeth/layer2=true
netcfg/confirm_static=true netcfg/disable_dhcp=true
netcfg/get_ipaddress=9.152.162.158 netcfg/get_netmask=255.255.252.0
netcfg/get_gateway=9.152.160.1 netcfg/get_nameservers=9.152.120.241
netcfg/get_hostname=s8330008 netcfg/get_domain=boeblingen.de.ibm.com
network-console/password=******** network-console/password-again=********
preseed/url=http://bistro/ubuntu/tarball/s8330008.preseed

------- Comment From <email address hidden> 2016-03-22 12:22 EDT-------
When installation is complete, I checked /target/etc/network/interfaces.d/ before reboot - it was empty:

~ # ls -l /target/etc/network/interfaces.d/
~ #

This explains, why the very first reboot works as expected. During the first reboot after installation, when network is already up, somebody adds the file encf5f0 to /etc/network/interfaces.d/, containing the inappropriate dhcp statement.