Bug 33363 – Samba4 migration - Update Scenario 1 - Improve migrate-sid.py

Bug 33363 - Samba4 migration - Update Scenario 1 - Improve migrate-sid.py


Summary:	Samba4 migration - Update Scenario 1 - Improve migrate-sid.py

Status:	RESOLVED WONTFIX

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

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Arvid Requate
QA Contact:

URL:
Keywords:

Depends on:	33234
Blocks:
	Show dependency tree / graph

Reported:	2013-11-13 18:07 CET by Arvid Requate
Modified:	2017-04-20 18:11 CEST (History)
CC List:	4 users (show)

See Also:
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 Arvid Requate

2013-11-13 18:07:13 CET

The script univention-samba4/scripts/migrate-sid.py should be adjusted to deal with samba accounts that do not have the attribute univentionSamba4SID:


1. UCS hosts without "Samba 4"
2. The group "Windows Hosts"


+++ This bug was initially created as a clone of Bug #33234 +++

Comment 1 Arvid Requate

2013-11-13 18:10:15 CET

In the case of the group "Windows Hosts", the corresponding Samba4 group should be looked up to fetch the new SID (from the new Samba4 domain).

Comment 2 Arvid Requate

2017-04-20 18:11:31 CEST

To my knowledge migration scenario 1 is not attractive and most customers use scenario 2 (in place migration), which works well enough.