Univention Bugzilla – Full Text Bug Listing |
Summary: | AD Connector treats DC Master object as computers/windows_domaincontroller | ||
---|---|---|---|
Product: | UCS | Reporter: | Florian Best <best> |
Component: | AD Connector | Assignee: | Florian Best <best> |
Status: | CLOSED FIXED | QA Contact: | Felix Botner <botner> |
Severity: | minor | ||
Priority: | P3 | CC: | best, ebersbach, gohmann, heidelberger, klaeser, oyen, requate, steuwer |
Version: | UCS 4.2 | Flags: | best:
Patch_Available+
|
Target Milestone: | UCS 4.2-2-errata | ||
Hardware: | Other | ||
OS: | Linux | ||
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?: | 2: Will only affect a 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.091 | Enterprise Customer affected?: | |
School Customer affected?: | ISV affected?: | ||
Waiting Support: | Flags outvoted (downgraded) after PO Review: | ||
Ticket number: | Bug group (optional): | Cleanup, Troubleshooting, Usability | |
Max CVSS v3 score: | |||
Bug Depends on: | 11658, 18501, 35559, 40839 | ||
Bug Blocks: | 30368 | ||
Attachments: | patch |
Description
Florian Best
2017-07-16 20:25:14 CEST
This doesn't break anything because the mapping in the AD connector doesn't synchronize the DC computer objects. Created attachment 9039 [details]
patch
Squashed patch.
(In reply to Florian Best from comment #1) > This doesn't break anything because the mapping in the AD connector doesn't > synchronize the DC computer objects. It seems I am wrong. The Jenkins test from today show that the traceback also occur there. univention-ad-connector (11.0.6-10): r81241 | Bug #45011: fix handling of object types univention-ad-connector.yaml: NONE | YAML Bug #45011 Bug #45037 (In reply to Florian Best from comment #3) > (In reply to Florian Best from comment #1) > > This doesn't break anything because the mapping in the AD connector doesn't > > synchronize the DC computer objects. > It seems I am wrong. The Jenkins test from today show that the traceback > also occur there. But this is only of cosmetic nature because we don't sync the computer (DC Master) object from AD to UCS. The ignore_filter() was just called after trying to determine the object type of the object with the computer-types from the mapping (which doesn't include computers/domaincontroller_master). univention-ad-connector (11.0.6-11): r81295 | Bug #45011: don't log tracebacks for objects which are ignored nevertheless The logfiles before showed: """ (ERROR ): get_ucs_object: could not identify UDM object type: cn=admember226a,cn=dc,cn=computers,dc=autotest226a,dc=local (PROCESS): get_ucs_object: using default: computers/windows (WARNING): get_ucs_object: failure was: (WARNING): Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/univention/connector/__init__.py", line 836, in get_ucs_object ucs_object = univention.admin.objects.get(module, co=None, lo=self.lo, position='', dn=searchdn) File "/usr/lib/pymodules/python2.7/univention/admin/objects.py", line 90, in get raise univention.admin.uexceptions.wrongObjectType('The object %s is not a %s.' % (dn, module.module,)) wrongObjectType: The object cn=admember226a,cn=dc,cn=computers,dc=autotest226a,dc=local is not a computers/windows. (PROCESS): sync to ucs: [windowscomputer] [ add] cn=admember226a,cn=dc,cn=computers,dc=autotest226a,dc=local (PROCESS): The object (cn=admember226a,cn=dc,cn=computers,dc=autotest226a,dc=local) will be ignored because a valid match filter for this object was not found. """ Now it only displays: """ (PROCESS): The object 'cn=admember222,cn=dc,cn=computers,dc=autotest222,dc=local' will be ignored because a valid match filter for this object was not found. """ *** Bug 44770 has been marked as a duplicate of this bug. *** OK, connector uses the correct udm module OK, YAML |