Bug 36817 – Service "Samba 4" registered on master even when S3->S4 migration failed

Bug 36817 - Service "Samba 4" registered on master even when S3->S4 migration failed


Summary:	Service "Samba 4" registered on master even when S3->S4 migration failed

Status:	RESOLVED WONTFIX

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-18 15:32 CET by Arvid Requate
Modified:	2020-07-03 20:51 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
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

2014-11-18 15:32:27 CET

Whe the in-place S3->S4 migration (setup-s4.sh) fails, the joinscript 98univention-samba still registeres the service "Samba 4" and marks the joinscript as successful. This makes it more difficult to fix the situation.

Comment 1 Ingo Steuwer

2020-07-03 20:51:03 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.