Bug 36802 – member mode can fail in DNS settings due to problems with Kerberos

Bug 36802 - member mode can fail in DNS settings due to problems with Kerberos


Summary:	member mode can fail in DNS settings due to problems with Kerberos

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	AD Connector
Version:	UCS 3.2
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Connector maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-11-18 12:09 CET by Ingo Steuwer
Modified:	2017-08-08 07:10 CEST (History)
CC List:	5 users (show)

See Also:	38285
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	5: Blocking further progress on the daily work
User Pain:	0.143
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2014111021000654
Bug group (optional):	Error handling, External feedback
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Ingo Steuwer

2014-11-18 12:09:57 CET

from 2014111021000654

Logfile from a member mode configuration:

-------------------------------
18.11.14 10:41:57.220  MODULE      ( PROCESS ) : Einrichten von
DNS-Einträgen...
18.11.14 10:41:57.426  MODULE      ( PROCESS ) : Create
_domaincontroller_master SRV record on 10.15.152.37
18.11.14 10:41:57.732  MODULE      ( PROCESS ) :
18.11.14 10:41:57.732  MODULE      ( ERROR   ) : ['kinit',
'--password-file=/etc/machine.secret', 'XXXXXXXXXXX\\$',
'nsupdate', '-v', '-g', '/tmp/tmpzamUoy'] failed with 1 (kinit:
krb5_get_init_creds: Client (XXXXXXXXXXX$@XXXXXXXXXX) unknown
)
18.11.14 10:41:57.732  MODULE      ( ERROR   ) : Join process failed
[failedToAddServiceRecordToAD]: failed to add SRV record to X.X.X.X
18.11.14 10:41:57.741  MODULE      ( ERROR   ) : Traceback:
Traceback (most recent call last):
  File
"/usr/lib/pymodules/python2.6/univention/management/console/modules/adconnector/__init__.py",
line 486, in admember_join
    admember.add_domaincontroller_srv_record_in_ad(ad_server_ip)
  File "/usr/lib/pymodules/python2.6/univention/lib/admember.py", line
643, in add_domaincontroller_srv_record_in_ad
    raise failedToAddServiceRecordToAD("failed to add SRV record to
%s" % ad_ip)
failedToAddServiceRecordToAD: failed to add SRV record to X.X.X.X
-------------------------------

In the second run the member mode has been configured successfully. Maybe we have some timing-issue with Kerberos here?

Comment 1 Stefan Gohmann

2015-03-12 08:30:33 CET

Removed errata status since it happened only once.

Comment 2 Arvid Requate

2016-09-28 12:58:53 CEST

I think this will be fixed by Bug 38285.

*** This bug has been marked as a duplicate of bug 38285 ***

Comment 3 Florian Best

2016-09-28 13:24:07 CEST

(In reply to Arvid Requate from comment #2)
> I think this will be fixed by Bug 38285.
> 
> *** This bug has been marked as a duplicate of bug 38285 ***

Why do you thing this? I did not dig into the code but the relation is not 100% obvious.

Comment 4 Stefan Gohmann

2017-06-16 20:35:46 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 5 Stefan Gohmann

2017-08-08 07:10:34 CEST

This issue has been filed against UCS 3.2.

UCS 3.2 is out of maintenance and many UCS components have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.