http://bugzilla.suse.com/show_bug.cgi?id=1010611 http://bugzilla.suse.com/show_bug.cgi?id=1010611#c1 Imobach Gonzalez Sosa changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |igonzalezsosa@suse.com Depends on| |984890 Assignee|yast2-maintainers@suse.de |yast-internal@suse.de --- Comment #1 from Imobach Gonzalez Sosa --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010611 http://bugzilla.suse.com/show_bug.cgi?id=1010611#c3 Knut Alejandro Anderssen González changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kanderssen@suse.com --- Comment #3 from Knut Alejandro Anderssen González --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010611 http://bugzilla.suse.com/show_bug.cgi?id=1010611#c5 --- Comment #5 from Tomas Kuchta --- Created attachment 702590 --> http://bugzilla.suse.com/attachment.cgi?id=702590&action=edit /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 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010611 http://bugzilla.suse.com/show_bug.cgi?id=1010611#c7 --- Comment #7 from Tomas Kuchta --- 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 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1010611 http://bugzilla.suse.com/show_bug.cgi?id=1010611#c9 Knut Alejandro Anderssen González changed: What |Removed |Added ---------------------------------------------------------------------------- Status|IN_PROGRESS |RESOLVED Resolution|--- |FIXED --- Comment #9 from Knut Alejandro Anderssen González --- 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-sprin... 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! ;) -- You are receiving this mail because: You are on the CC list for the bug.