Bug 803422

Summary:	Unable to manage network settings
Product:	[openSUSE] openSUSE 12.3	Reporter:	Charles Arnold <carnold>
Component:	Network	Assignee:	Michal Filka <mfilka>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Critical
Priority:	P1 - Urgent	CC:	donald.vosburg, jdouglas, jfehlig, locilka, mfilka, mt, tgoettlicher
Version:	RC 1	Flags:	coolo: SHIP_STOPPER-
Target Milestone:	---
Hardware:	x86-64
OS:	SUSE Other
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	y2logs from the first test machine y2logs from the second test machine

Description Charles Arnold 2013-02-13 00:20:27 UTC

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).

Comment 1 Michal Filka 2013-02-15 08:40:21 UTC

Attach logs, please. You can use save_y2logs. Thanks.

Comment 2 Charles Arnold 2013-02-15 15:07:45 UTC

Created attachment 524891 [details]
y2logs from the first test machine

Comment 3 Charles Arnold 2013-02-15 15:08:40 UTC

Created attachment 524892 [details]
y2logs from the second test machine

Comment 4 Stephan Kulow 2013-02-18 11:59:10 UTC

I blame the sysconfig 0.8 update ;(

Comment 5 Michal Filka 2013-02-18 12:13:21 UTC

There is a batch of related patches for yast. It is under review now.

Comment 6 Thomas Göttlicher 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.

Comment 7 Charles Arnold 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.

Comment 9 Lukas Ocilka 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?

Comment 10 Michal Filka 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

Comment 11 Charles Arnold 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.

Comment 12 Stephan Kulow 2013-03-01 10:40:26 UTC

the network on first boot is something I accept as known bug (we had something similiar in 12.2)

Comment 13 Michal Filka 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.

Comment 14 Michal Filka 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 ***