[Bug 803422] New: Unable to manage network settings
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c0 Summary: Unable to manage network settings Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: carnold@suse.com QAContact: qa-bugs@suse.de CC: jdouglas@suse.com, jfehlig@suse.com, mt@suse.com, llipavsky@suse.com Found By: Development Blocker: --- The tools used to manage the network are broken in the following ways after an installation. To reproduce. 1) First do an install of openSUSE 12.3 RC1 x86_64. 2) Accept the defaults (I also opened the ssh port). 3) Run zypper update to get all the latest updates. At this point my experience is that you have a functioning network and all is well. The problem begins when you want to change or add something. For example. 1. 'rcnetwork stop' does nothing. It states that it is redirecting to "systemctl stop network.service" (NetworkManager.service) but this actually does nothing. So neither the if<commands> or the systemctl commands for networking seem to do work. 2. Running 'yast2 lan' by default shows 'Traditional Method with ifup' on the Network Setup Method which seems untrue. If for example you create a bridge in yast, it is not reflected in the system. Neither 'ifconfig' nor 'brctl show' will show it. Yet it will remain defined in yast. 3. When I run 'Configure Desktop' -> 'Network Settings', it doesn't show the default interface created during installation (in my case, eth0). I'm not familiar with how this should work - just guessing that eth0 should show up as a wired connection. In summary, a working network is created at install time but none of the tools seem to be able to manage it or inter-operate. This becomes a critical problem for virtualization which requires us to be able to create a bridge before installing any guest. When running the yast2-vm tool to install Xen or KVM it asks to install a bridge and seems to work - and yet doesn't (it is just calling into the yast networking code to do this). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High CC|llipavsky@suse.com |locilka@suse.com, | |mfilka@suse.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c1 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |carnold@suse.com --- Comment #1 from Michal Filka <mfilka@suse.com> 2013-02-15 08:40:21 UTC --- Attach logs, please. You can use save_y2logs. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c2 --- Comment #2 from Charles Arnold <carnold@suse.com> 2013-02-15 15:07:45 UTC --- Created an attachment (id=524891) --> (http://bugzilla.novell.com/attachment.cgi?id=524891) y2logs from the first test machine -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c3 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|carnold@suse.com | --- Comment #3 from Charles Arnold <carnold@suse.com> 2013-02-15 15:08:40 UTC --- Created an attachment (id=524892) --> (http://bugzilla.novell.com/attachment.cgi?id=524892) y2logs from the second test machine -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c4 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER+ --- Comment #4 from Stephan Kulow <coolo@suse.com> 2013-02-18 12:59:10 CET --- I blame the sysconfig 0.8 update ;( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c5 --- Comment #5 from Michal Filka <mfilka@suse.com> 2013-02-18 12:13:21 UTC --- There is a batch of related patches for yast. It is under review now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c6 Thomas Göttlicher <tgoettlicher@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tgoettlicher@suse.com AssignedTo|yast2-maintainers@suse.de |mfilka@suse.com --- Comment #6 from Thomas Göttlicher <tgoettlicher@suse.com> 2013-02-22 16:13:02 UTC --- (In reply to comment #5)
There is a batch of related patches for yast. It is under review now. Michal, could you please keep an eye on this issue and close this bug as soon as it's fixed in yast.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c7 Charles Arnold <carnold@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 - High |P1 - Urgent --- Comment #7 from Charles Arnold <carnold@suse.com> 2013-02-25 16:29:37 UTC --- The RC2 checkin deadline is just about here. I am ready to test any fixes when they become available. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c9 --- Comment #9 from Lukas Ocilka <locilka@suse.com> 2013-02-25 16:34:58 UTC --- (In reply to comment #5)
There is a batch of related patches for yast. It is under review now.
Michal, what's the current status of these patches? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c10 --- Comment #10 from Michal Filka <mfilka@suse.com> 2013-02-26 15:17:54 UTC --- (In reply to comment #9)
(In reply to comment #5)
There is a batch of related patches for yast. It is under review now.
Michal, what's the current status of these patches?
Review done, not merged https://github.com/yast/yast-network/pull/47 https://github.com/yast/yast-yast2/issues/44 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c11 --- Comment #11 from Charles Arnold <carnold@suse.com> 2013-02-27 20:30:14 UTC --- Some results from testing Build0094 (x86_64). 1) After a default install and on the first login the network needs to be started manually (ifconfig only shows the loopback). I don't know if this would be true if I had just rebooted first. Once started, it was up on subsequent reboots. 2) rcnetwork start and stop works. 3) Running 'yast2 lan' displays the warning about the default being Network Manager which is correct. Selecting 'ifup' correctly switches the setup method. 4) Running 'yast2 xen' and installing Xen and choosing to create a bridge works. The bridge is created and is persistent across reboots. In summary, everything seems to be working accept for the network not being started on the very first login when the installation completes. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c12 Stephan Kulow <coolo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag|SHIP_STOPPER+ |SHIP_STOPPER- --- Comment #12 from Stephan Kulow <coolo@suse.com> 2013-03-01 11:40:26 CET --- the network on first boot is something I accept as known bug (we had something similiar in 12.2) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c13 --- Comment #13 from Michal Filka <mfilka@suse.com> 2013-03-19 05:55:49 UTC --- I've patched yast2-install a couple of days ago. See https://github.com/yast/yast-installation/pull/28. It probably fixes the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=803422 https://bugzilla.novell.com/show_bug.cgi?id=803422#c14 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE --- Comment #14 from Michal Filka <mfilka@suse.com> 2013-03-19 05:57:52 UTC --- According comment#11 & comment#12 I'm going to mark the bug as duplicate of bnc#808039. *** This bug has been marked as a duplicate of bug 808039 *** http://bugzilla.novell.com/show_bug.cgi?id=808039 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com