Bug 1010611

This problem should be gone when we fix bug 984890. The team is already working in a fix: https://github.com/yast/yast-network/pull/461.

By the way, thanks for reporting!

Thomas, 

Although we are currently working in a solution, we always ask for YaST logs https://en.opensuse.org/openSUSE:Report_a_YaST_bug.

So I suppose that you are using wicked and that you did a normal installation without linuxrc options.

Could you apart of yast logs attach the content of /etc/sysconfig/network at least the configuration of your interace and the dhcp file.

Created attachment 702589 [details]
yast2 logs collected by save_y2logs /tmp/y2logs.tgz

Created attachment 702590 [details]
/etc/sysconfig/network logs

Attached please find Yast2 log files and sysconfig/network files.

My installation was standard remote install executed over VNC in UEFI Bios. Nothing significant was customized at boot or at install.

I started VNC remote install by editing Grub at boot - adding vnc=1 vncpassword=.... to linuxefi line and booting by F10 (I preferred the old non UEFI way of just adding the boot options ... anyway)

Post install, I experimented with btrfs and snapper on separate hard drive pair.

I hope it helps, Tomas

So confirmed my suspicions :), as part of the current sprint we will provide some documentation about current network behaviour during installation, autoinstallation and in a running system through the lan client. This is the beginning of the linuxrc section I have started to write:

---
By default linuxrc does not configure any interface except in the case that we specify some special options as for example enabling vnc, ssh or with the ifcfg option ifcfg=*=dhcp. If any of this options is given, linuxrc will create a ifcfg file with this options:

BOOTPROTO='dhcp'
STARTMODE='auto'
DHCLIENT_SET_HOSTNAME='yes'
---

And this is exactly what you have in your ifcfg file because your vnc installation. Currently YaST only permit to change the global value DHCLIENT_SET_HOSTNAME in /etc/sysconfig/network/dhcp but not the interfaces attribute and that is exactly what we are fixing/adding in the pull request commented by Imobach, so should be available soon, by now you can just remove the DHCLIENT_SET_HOSTNAME entry from the interface file.

Thank you Alejandro

I understand that I can modify the interface file post instal.

Just out of curiosity:
Could I also avoid the this problem if I use autoyast=autoinst.xml boot option in unattended installation instead of remote vnc/ssh?

Thank you for looking into this and scheduling it for fix, Tomas

In case of autoyast then linuxrc should not configure the network but it does for autoyast2 as it fetchs the profile to use the linuxrc options.

So basically always that linuxrc needs network and not static configuration is provided it will create the dhcp configuration commented before.

And here are some links to the changes that have been done:

First of all, just take a look to our blog entry which already explains some of the changes related to dhcp hostname set:

https://lizards.opensuse.org/2016/12/02/highlights-of-yast-development-sprint-28/

And here some of the pull requests involved:

https://github.com/yast/yast-network/pull/461
https://github.com/yast/yast-network/pull/477

About the network documentation for installation and autoinstallation, although these documents are more developer oriented maybe not very user friendly ;) sorry for that:

https://github.com/yast/yast-network/blob/master/doc/installation.md
https://github.com/yast/yast-network/blob/master/doc/autoinstallation.md

So I think that we could mark this bug as fixed,invalid or duplicated of 984890.

Thnx for the report! ;)

Thank you very much to everyone for closing this.

Tomas