Bug 55877 - School replica join: 98univention-samba4-dns.inst waits for replicated dns-(hostname) entry in samba [4.4]
School replica join: 98univention-samba4-dns.inst waits for replicated dns-(h...
Status: NEW
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on: 54791 55880
Blocks: 55137 55218
  Show dependency treegraph
 
Reported: 2023-03-14 13:26 CET by Christina Scheinig
Modified: 2023-03-14 17:36 CET (History)
7 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 6: Setup Problem: Issue for the setup process
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 4: A User would return the product
User Pain: 0.137
Enterprise Customer affected?:
School Customer affected?: Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023031421000378
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2023-03-14 13:26:19 CET
In the customer environment it takes immense time to replicate the objectClass=dnsZone Objects.
Therefor the 98univention-samba4-dns.inst joinscripts waits hours until the SPN account dns-($hostname) entry is finally existing in samba.

So unfortunately the bugfix from Bug #54791 is not entirely helping.




+++ This bug was initially created as a clone of Bug #54791 +++

At a school customer, with ~150.000 users, we've seen the following error pretty often during the join of a new school replica server:


Wait for bind9: .Restarting bind9 (via systemctl): bind9.service.
Restarting samba-ad-dc (via systemctl): samba-ad-dc.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.
....................................................................................................Restarting bind9 (via systemctl): bind9.service.

See "systemctl status bind9.service" and "journalctl -xe" for details.
 failed!
**************************************************************
* ERROR: Failed to configure Samba4 as backend for bind.     *
*        Please check the samba and the s4-connector logfile.*
**************************************************************


This happened, because during the join thousands of objects have been created in UCS and have been added as pickle files for the s4connector. 
When starting the s4connector during the join, all those files are then processed in order of creation.
Oftentimes, the DNS zones necessary for this joinscript are not synced before the timeout of ~20 minutes is reached.
The customer then has to wait until the zone is synced and restart the join.
It would be good if we could sync the objects needed for the join to complete earlier than the other less important objects.