Bug 35180 – inconsistent behavior of " --keep-existing" (keep the SID) during samba4 join

Bug 35180 - inconsistent behavior of " --keep-existing" (keep the SID) during samba4 join


Summary:	inconsistent behavior of " --keep-existing" (keep the SID) during samba4 join

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-06-24 09:20 CEST by Felix Botner
Modified:	2020-07-03 20:55 CEST (History)
CC List:	1 user (show)

See Also:	40661
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.017
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
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 Felix Botner

2014-06-24 09:20:44 CEST

I have a s4 master and s4 slave, now i join the slave to the s4 domain. Then i rerun the samba4 join script, but the samba4 join fails (e.g. server not available). 

After the next samba4 join, my slave has a new SID.

The problem is that, "--keep-existing" is set if the join script finds an account in the local sam.db. But during join the sam.db is deleted (cleanup_var_lib_samba), so after a failed join,  "--keep-existing" is never used.

Comment 1 Ingo Steuwer

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