Bug 41409 – Joining Samba systems should check if S4-Connector is running anywhere at all

Bug 41409 - Joining Samba systems should check if S4-Connector is running anywhere at all


Summary:	Joining Samba systems should check if S4-Connector is running anywhere at all

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Samba4
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P5 enhancement (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-06-01 16:21 CEST by Arvid Requate
Modified:	2020-07-03 20:52 CEST (History)
CC List:	2 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a few 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.046
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	Error handling
Max CVSS v3 score:

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 Arvid Requate

2016-06-01 16:21:46 CEST

In case a UCS system joins a Samba/AD domains the univention-samba and univention-samba4 joinscripts should first check if there is *any* system that registered univentionService=S4-Connector.

We had one support case, where the S4-Connector was installed on a DC-Backup but the S4-Connector Joinscripts had not been executed. Then the customer joined a Memberserver with Samba and was surprised to find that share access was not working for users.

I guess the simple check proposed above would have prevented this at an earlier stage. One could additionally check if that S4-Connector host has any unexecuted joinscripts , but that may not even be necessary in the first step.

Comment 1 Ingo Steuwer

2020-07-03 20:52:21 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.