Bug 17289

Summary:	If networkmanager service is unselected in installer summary, it shows enabled after reboot
Product:	Mageia	Reporter:	Dick Gevers <dvgevers>
Component:	Installer	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ftg, luke.nukem.jones, mageia, marja11, ngompa13
Version:	Cauldron	Keywords:	6dev1, NEEDINFO
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	installer or drakconnect?	CVE:
Status comment:

Description Dick Gevers 2015-12-04 15:54:15 CET

Description of problem:

Install from classical iso dated 29/11, proceed to summary.

From experience I know networkmanager does not (did not) work with my hardware and wpa_supplicant works, so in Summary --> Services I select wpa_supplicant and make sure networkmanager service is not enabled (flag removed).

But after reboot I see:

"systemctl status"  ....."vendor preset: enabled" 

which I would imagine is not correct: I think it overrides my choice...



Reproducible: 

Steps to Reproduce:

Dick Gevers 2015-12-04 15:54:25 CET

Whiteboard: (none) => 6dev1

Comment 1 Luke Jones 2015-12-04 22:16:57 CET

It may be that the service scripts have been updated. My understanding is that NetworkManager will start wpa_supplicant when required.

However I am not sure if the wpa_supplicant service has a script requirement for NetworkManager, the easiest way to check would be to open the service file and are if it refers to it.

I'm not near a computer at the moment so am unable to check for you.

CC: (none) => luke.nukem.jones

Comment 2 Dick Gevers 2015-12-05 12:26:29 CET

It seems to me that you are looking at the setup working as intended. Fine.

But I was looking at the behaviour of the whole setup if the user decides it should be otherwise: user overrules default setup. This should also work, because the options are allowing it... To me it looks like that is not the case now so I signal it and let the experts judge it.

Comment 3 Frank Griffin 2015-12-05 14:16:25 CET

I just went through this with something else.  I'm not sure what "vendor preset: enabled" means, but it's not the same as "enabled".  You should see "enabled" or "disabled" right before this on the output line.

My experience is that NM is *not* enabled by default in new systems (I usually have to do it myself), so for what you want, the better course would be to ignore NM entirely.  In Summary, select Network and configure your wireless but when you get to the panel that asks whether NM should control the interface, choose "No".  Let the regular MGA network stuff worry about wpa_supplicant.

The way this is *supposed* to work is that drakconnect creates an ifcfg file for the interface and specifies NM=NO in it.  Whether NM is running or not in the new system, it looks for the ifcfg file and keeps its hands off of the interface if NM=NO is specified.

This didn't always work as intended.  In the early days of NM, you pretty much had to uninstall it to get it not to interfere.  Hopefully, it's feeling much better now.

CC: (none) => ftg

Samuel Verschelde 2015-12-07 12:14:52 CET

CC: (none) => mageia
Assignee: bugsquad => thierry.vignaud
Source RPM: classical iso dated 29/11 => installer or drakconnect?

Comment 4 Neal Gompa 2015-12-11 14:36:46 CET

@Frank: The NM_CONTROLLED= parameter does work correctly now, so if you specify NM_CONTROLLED=no, NetworkManager will ignore the interface.

CC: (none) => ngompa13

Comment 5 Frank Griffin 2015-12-11 14:47:30 CET

Thanks, Neal.  I couldn't be sure, since I've long since disabled ifcfg-rh in /etc/NetworkManager/NetworkManager.conf and let NM handle everything.

Comment 6 Marja Van Waes 2016-04-05 19:32:39 CEST

Is this bug still valid for the released 6dev1 iso(s)?

Keywords: (none) => 6dev1, NEEDINFO
CC: (none) => marja11
Whiteboard: 6dev1 => (none)

Comment 7 Dick Gevers 2016-04-07 13:36:57 CEST

AFAICT from the journalctl records of the 6dev1 install, nm is not activated, so it appears to be fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED