Univention Bugzilla – Bug 44103
DNS zone sync_to_ucs fails due to unexpected uppercase DC attribute
Last modified: 2019-01-03 07:20:36 CET
Created attachment 8663 [details] DC_case.patch In an AD-Takeover customer environment synchronization of some reverse DNS zones failed in the S4-Connector sync_to_ucs direction because the SOA objects DC=@ from Samba/AD where not identified properly as such by _identify_dns_con_object. The reason was, that the attribute was not lowercase "dc: " but uppercase. The attached patch fixed the issue and would improve robustness of the product.
(In reply to Arvid Requate from comment #0) > Created attachment 8663 [details] > DC_case.patch > + try: > + dc_vals = [value for key, value in object['attributes'].iteritems() if 'dc' == key.lower()][0] > + except IndexError: > + dc = None > + else: > + dc = dc_vals[0] Should be: + try: + dc = [value for key, value in object['attributes'].iteritems() if 'dc' == key.lower()][0] + except IndexError: + dc = None As `dc` must be a list() of DC values. With the else branch you would later only get the first char instead of the first DC value with `dc[0]`.
No, value is a list.
Created attachment 8666 [details] DC_case.patch Sorry, you are right, no clue why it solved the issue then. Anyway, this is the fixed patch.
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.