802473 – NetwokrManager is started unconditionally

Bug 802473 - NetwokrManager is started unconditionally

Summary: NetwokrManager is started unconditionally

Status:	RESOLVED DUPLICATE of bug 803058

Alias:	None

Product:	openSUSE 12.3
Classification:	openSUSE
Component:	Network (show other bugs)
Version:	RC 1
Hardware:	x86-64 Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	Marius Tomaschewski
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2013-02-06 22:08 UTC by Olivier Nicolas
Modified:	2013-02-26 17:06 UTC (History)
CC List:	0 users

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

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 Olivier Nicolas 2013-02-06 22:08:56 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0

After upgrade from 12.3 Beta to 12.3 RC1, NetworkManager is started unconditionally even if NETWORKMANAGER="no"


Reproducible: Always

Steps to Reproduce:
1. Run 12.3 Beta with  NETWORKMANAGER="no" without problem. NM is not started
2. Upgrade 12.3 Beta to 12.3 RC1
3. 
Actual Results:  
NM is always started 

Expected Results:  
NM should not start if NETWORKMANAGER is set to "no" in /etc/sysconfig/network/config

Start Yast and checked that Network Setup Method is set to "Traditional Method with ifup". After a reboot NM is still started at boot.


Workaround: manually disable NM with "systemctl disable NetworkManager.service"

Comment 1 Marius Tomaschewski 2013-02-26 17:06:57 UTC

The migration of
- NETWORKMANAGER="no" is fixed and submitted + accepted (rq#156054,rq#156065),
- NETWORKMANAGER="yes" submitted in rq#156055 for review by NM maintainers as
  there are some NM + systemd + update related issues.

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