Bug 38713 - S4-Connector traceback while synchronizing tombstoned DNS records.
S4-Connector traceback while synchronizing tombstoned DNS records.
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 4.2
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-06-16 17:08 CEST by Arvid Requate
Modified: 2020-07-03 20:55 CEST (History)
1 user (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?: 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.069
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2015061221000391
Bug group (optional): Error handling
Max CVSS v3 score:
requate: Patch_Available+


Attachments
DNS_TYPE_TOMBSTONE.patch (554 bytes, patch)
2015-06-16 17:34 CEST, Arvid Requate
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2015-06-16 17:08:05 CEST
Ticket#2015061221000391 showed an S4-Connector traceback due to a DNS PTR record object in Samba4 that was falsely identified as host_record instead:

15.06.2015 13:09:45,640 LDAP        (INFO   ): dns con2ucs: Object (DC=123,dc=123.123.123.in-addr.arpa,cn=dns,dc=foo,dc=local) is from type host_record

Looking at the Samba4 Object data shows that this was a tombstoned object:

'dNSTombstoned': [u'TRUE'] and the dnsRecord blob has the  wType:  DNS_TYPE_TOMBSTONE.

The univention.s4.dns._identify_dns_con_object function should be adjusted to ignore these objects.
Comment 1 Arvid Requate univentionstaff 2015-06-16 17:34:06 CEST
Created attachment 6966 [details]
DNS_TYPE_TOMBSTONE.patch
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:40:50 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Ingo Steuwer univentionstaff 2020-07-03 20:55:46 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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