Univention Bugzilla – Bug 41025
S4-Connector: sync_to_ucs fails with Traceback 'NoneType' object has no attribute '__getitem__'
Last modified: 2019-01-03 07:16:37 CET
UCS 4.0-4 errata 408, UCS@school 4.0 R2 (ucsschool_20160115) A customer experiences the following traceback on almost every school slave: > 08.04.2016 15:04:21,328 LDAP (PROCESS): sync to ucs: Resync rejected dn: cn=machinestaging,CN={FDF1B411-DD04-4122-956B-8F90930C430F},CN=Policies,CN=System,DC=schule,DC=de > 08.04.2016 15:04:21,335 LDAP (PROCESS): sync to ucs: [ container] [ delete] cn=machinestaging,cn={fdf1b411-dd04-4122-956b-8f90930c430f},cn=policies,cn=system,DC=schule,DC=de > 08.04.2016 15:04:21,731 LDAP (WARNING): delete subobject: cn=microsoft,cn=machinestaging,cn={fdf1b411-dd04-4122-956b-8f90930c430f},cn=policies,cn=system,DC=schule,DC=de > 08.04.2016 15:04:21,734 LDAP (PROCESS): sync to ucs: [ container] [ delete] cn=microsoft,cn=machinestaging,cn={FDF1B411-DD04-4122-956B-8F90930C430F},cn=Policies,cn=System,DC=schule,DC=de > 08.04.2016 15:04:22,126 LDAP (WARNING): delete subobject: cn=windows,cn=microsoft,cn=machinestaging,cn={fdf1b411-dd04-4122-956b-8f90930c430f},cn=policies,cn=system,DC=schule,DC=de > 08.04.2016 15:04:22,130 LDAP (PROCESS): sync to ucs: [ container] [ delete] cn=windows,cn=microsoft,cn=machinestaging,cn={FDF1B411-DD04-4122-956B-8F90930C430F},cn=Policies,cn=System,DC=schule,DC=de > 08.04.2016 15:04:22,191 LDAP (ERROR ): Unknown Exception during sync_to_ucs > 08.04.2016 15:04:22,192 LDAP (ERROR ): Traceback (most recent call last): > File "/usr/lib/pymodules/python2.7/univention/s4connector/__init__.py", line 1411, in sync_to_ucs > guid_unicode = original_object.get('attributes').get('objectGUID')[0] > TypeError: 'NoneType' object has no attribute '__getitem__' I will attach the log with connector/debug/level='4' at Ticket#2016040421000103
I guess we need to check which objectclass cn=microsoft and cn=microsoft have in cases like these. Maybe the con_subtree_delete_objects filter (Bug 33882) just needs to be extended. If that is the case, then Bug 45311 should be considered too.
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016. Customers still on UCS 4.0 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.