Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
This is related to bug 748831. Even with the fixed winbind krb5 locator (or without it) net ads join occasionally fails to kinit for DNS update in domains with multiple DCs unless:
1) krb5.conf has both kdc and master_kdc set to a certain DC and KDC DNS lookup is disabled
2) the same DC is passed to net ads join with the -S parameter
3) create krb5 conf = no is set in smb.conf
If any of the above steps is ignored then occasionally net ads join first communicates with one DC during machine account creation and then when preparing for DNS update and doing kerberos_kinit_password / krb5_get_init_creds_password another DC is contacted (as seen in krb5 trace) which is not yet in sync with the earlierly contacted DC (as everything happens in a timeframe of a few seconds which is too short for DCs to update their records) causing errors like:
...
kerberos_kinit_password: as SMBTEST$@EXAMPLE.COM using [MEMORY:net_ads] as ccache and config [(null)]
kerberos_kinit_password SMBTEST$@EXAMPLE.COM failed: Client not found in Kerberos database
name_to_fqdn: lookup for SMBTEST -> smbtest.example.com.
...
Joined 'SMBTEST' to realm 'EXAMPLE.COM'
DNS Update for smbtest.example.com failed: ERROR_DNS_GSS_ERROR
net ads join should always communicate with only one DC in order to prevent errors like this.
Version-Release number of selected component (if applicable):
samba-3.6.8-130.el6.x86_64
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-0409.html