Bug 3740

Summary:	Installer selected services - flags in summary - systemd defaults - drakxservices ready for it?
Product:	Mageia	Reporter:	Dick Gevers <dvgevers>
Component:	Installer	Assignee:	Thierry Vignaud <thierry.vignaud>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	dmorganec, jm.sarat, mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	drakxtools-13.72.1-1.mga2	CVE:
Status comment:
Bug Depends on:
Bug Blocks:	2120
Attachments:	requested chkconfig --list requested 'systemctl list-units'

Description Dick Gevers 2011-12-14 09:44:55 CET

Description of problem:

Earlier I reported https://bugs.mageia.org/show_bug.cgi?id=37 which still holds true (mdadm running in every install by default even though no raid/lvm etc. even on a laptop).

Now I'm afraid I see more of the same: with systemctl list-units I see that are activated:
fedora-storage-init.service and *-late.service are 'active, exited'
even on a laptop which is not logical, being for RAID. LVM etc. Also, if possible, they shouldn't be activated on a laptop.

Moreover, some flags removed in the installer summary are effectively not honoured: ip6tables and rpcbind were unflagged for not needing to run, but once installation was finished they were running.

I suppose drakx' services manipulation needs adaptation to systemd !?!?

Moreover, ifconfig after completing install shows I have an inet6 address for eth0 which is not logical comparing the unflagging of ip6tables in install summary (reason: my modem now in use does not support ipv6 but is more convenient for this house then one that does).

$ $ $

Finally, I see while running LiveCD's that iptables and shorewall are running okay protecting the machine. But ifconfig also show an inet6 address assigned to eth0, but at the same time services ip6tables and shorewall6 are not running, and I guess not even packed on the media. That is not consistent with ipv4 behaviour.
If needed I can report this seaparely.

Above is for alpha2 prerelease isos of 2011-12-12.

Dick Gevers 2011-12-14 09:46:48 CET

Blocks: (none) => 2120

Comment 1 Manuel Hiebel 2011-12-14 13:02:23 CET

iirc drakxservices use chkconfig.
So maybe you can attach the list of status from systemctl and chkconfig

added the package maintainer.

CC: (none) => dmorganec
Assignee: bugsquad => thierry.vignaud

Comment 2 Dick Gevers 2011-12-14 16:04:47 CET

Created attachment 1237 [details]
requested chkconfig --list

Comment 3 Dick Gevers 2011-12-14 16:06:06 CET

Created attachment 1238 [details]
requested 'systemctl list-units'

THis is from the 12/12 isos!

Comment 4 Dick Gevers 2011-12-15 11:29:50 CET

New install (from the 15/12 iso, 64 bits:

Networkmanager flagged off as not wanted. chkconfig lists it as 7x off, but systemctl list-units shows:

NetworkManager.service     loaded active running   Network Manager

Comment 5 D Morgan 2012-01-28 02:50:19 CET

(In reply to comment #4)
> New install (from the 15/12 iso, 64 bits:
> 
> Networkmanager flagged off as not wanted. chkconfig lists it as 7x off, but
> systemctl list-units shows:
> 
> NetworkManager.service     loaded active running   Network Manager

chkconfig does not work for systemd services

Comment 6 Manuel Hiebel 2012-03-12 19:44:54 CET

*** Bug 4910 has been marked as a duplicate of this bug. ***

CC: (none) => jm.sarat

Manuel Hiebel 2012-03-12 23:59:34 CET

Severity: normal => major

Comment 7 Colin Guthrie 2012-04-24 22:19:18 CEST

Issues relating to installer and services should be fixed in the next stage2 build (not yet released).

As for mdadm and other storage stuff, this is still a hard requirement for now.

Ideally you should make a note to make this more optional for mga3 (i.e. at the technical features phase) but I don't fancy breaking all that stuff out at this stage.

So I'll close this bug for now due to various fixes already included. Note that statically enabled services or complex services are not shown in the installer. This will require more reworking to be compatible with system and will happen in the mga3 timeframe.

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

Comment 8 Thierry Vignaud 2012-04-25 08:36:23 CEST

Actually I fixed "mdadm running in every install by default even though no raid/lvm" quite some time ago.