Bug 49215 – The module system service shows a samba4.service, but this does not excists

Bug 49215 - The module system service shows a samba4.service, but this does not excists


Summary:	The module system service shows a samba4.service, but this does not excists

Status:	RESOLVED DUPLICATE of bug 42241

Product:	UCS
Classification:	Unclassified
Component:	UMC - System services
Version:	UCS 4.4
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:	UMC maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-04-02 12:21 CEST by Christina Scheinig
Modified:	2019-04-02 12:41 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.034
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Problem_systemdienst (106.72 KB, image/png) 2019-04-02 12:21 CEST, Christina Scheinig	Details
View All 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 Christina Scheinig

2019-04-02 12:21:38 CEST

Created attachment 9952 [details]
Problem_systemdienst

The system service module shows a samba4.service for autostart. The customer wanted to start samba4, but got the attached message. samba4.service could not be found. That is true, we do not have a samba4.service.
The service for samba to be started is samba-ad-dc.service and this was already running.

I guess the module uses the ucr value samba4/autostart ?

Comment 1 Erik Damrose

2019-04-02 12:41:29 CEST


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