Bug 41302 – NoneType object traceback in primary_group_sync_from_ucs

Bug 41302 - NoneType object traceback in primary_group_sync_from_ucs


Summary:	NoneType object traceback in primary_group_sync_from_ucs

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Duplicates:	7854 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-05-19 21:09 CEST by Michel Smidt
Modified:	2019-01-03 07:23 CET (History)
CC List:	4 users (show)

See Also:	42522
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	1: Will affect a very 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:	2016090921000131
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.

Comment 1 Arvid Requate

2016-05-20 14:48:29 CEST

Could you add /var/lib/univention-connector/ad/1463575794.742703 ?

Comment 2 Michel Smidt 2016-05-24 18:01:40 CEST

(In reply to Arvid Requate from comment #1)
> Could you add /var/lib/univention-connector/ad/1463575794.742703 ?

I'am sorry, not.

Comment 3 Stefan Gohmann

2016-09-28 06:18:00 CEST

I don't think it is good idea to exclude the basic cn=users containers at least if the basic objects are part of it. The connector needs access to the primary group objects and by default the primary group object in AD is by default Domain Users or Domänen-Benutzer.

I saw the same traceback at Ticket #2016090921000131 and it seems to be the same customer. The traceback is the reason for the deactivation of the user. At least at Ticket #2016090921000131 the syncmode is sync and so the deactivated user is synced back.

Comment 4 Stefan Gohmann

2016-09-28 06:43:48 CEST

*** Bug 7854 has been marked as a duplicate of this bug. ***

Comment 5 Florian Best

2017-06-28 14:52:59 CEST

There is a Customer ID set so I set the flag "Enterprise Customer affected".

Comment 6 Stefan Gohmann

2019-01-03 07:23:18 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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