Bug 803521 - Networking: NetworkManager and Netconfig is swaped
Summary: Networking: NetworkManager and Netconfig is swaped
Status: RESOLVED DUPLICATE of bug 798348
Alias: None
Product: openSUSE 12.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: RC 1
Hardware: x86-64 Other
: P1 - Urgent : Major (vote)
Target Milestone: ---
Assignee: Marius Tomaschewski
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-13 13:50 UTC by Paul Zirnik
Modified: 2013-02-18 13:49 UTC (History)
2 users (show)

See Also:
Found By: SUSE Technical Services
Services Priority: 1000
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
coolo: SHIP_STOPPER+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Zirnik 2013-02-13 13:50:43 UTC 
I'm not sure if this is a plain YaST2 issue or not.

After installation in second Stage during network configuration following 
issue exist:

Network configuration is swaped

- the default is to use traditional via Netconfig, however if i keep this default
  setting NetworkManager will be used

- if i switch to NetworkManager the traditional method via Netconfig will be used

So either the labels are wrong or the functionality is wrong

You can verify this is the next dialog, where the internet connectivity
will be tested.

- if you have selected traditional method with Netconfig the connectivity test
  will fail, because of networkmanager is used

- if you have selected NetworkManager the test will succeed, because Netconfig
  will be used.  


I'm now going to test how it works after installation when network is configured via YaST2
Comment 1 Paul Zirnik 2013-02-13 14:06:24 UTC 
When network configuration is changed in YaST2 it makes no difference what is selected. Always NetworkManager will be configured/used.
Comment 2 Forgotten User xRcrmyYBVX 2013-02-13 14:59:27 UTC 
I can confirm this problem with a fresh installation using OS12.3RC1 Net DVD.

After fresh installation, network is up but 
# rcnetwork status
says that network manager is INACTIVE,
while YaST2 says that "ifup" is selected for network configuration.

After a reboot, network manager is now running, but still YaST shows "ifup" method to be used.
Comment 3 Forgotten User -L9sfYjG5A 2013-02-13 17:48:00 UTC 
Same here with oS12.3RC1 x64 full DVD.
Even changing between ifup and networkmanager doesn't do anything (I hoped to activate ifup with setting of networkmanager). This is bad because I don't use X and can't configure my network this way.
Comment 4 Marius Tomaschewski 2013-02-18 13:49:34 UTC 
sysconfig and most other packages has been changed to not use NETWORKMANAGER
variable any more, but a network.service alias link.

See also release notes bug #800771 and - still unfixed - bug #798348, to
adopt switching between NetworkManager and /etc/init.d/network in yast2.
[/etc/init.d/network is currently active only while miminal installation,
 in all other cases NetworkManager because yast2 is unable to switch it
 as needed.]

To enable NetworkManager, use:

  systemctl stop network.service
  systemctl --force enable NetworkManager.service
  systemctl start network.service

to disable NetworkManager, use:

  systemctl stop network.service
  systemctl --force disable NetworkManager.service
  systemctl start network.service

This command:
   systemctl --no-pager -p Id show network.service

reports "Id=NetworkManager.service" when NetworkManager acts as the network
service, "Id=network.service" means /etc/init.d/network.

*** This bug has been marked as a duplicate of bug 798348 ***