Bug 42310 – Login to UMC on DC Slave takes very long if UCS Master is down

Bug 42310 - Login to UMC on DC Slave takes very long if UCS Master is down


Summary:	Login to UMC on DC Slave takes very long if UCS Master is down

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-4-errata
Assigned To:	Florian Best
QA Contact:	Felix Botner

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-09-07 17:14 CEST by Michael Grandjean
Modified:	2016-11-16 14:12 CET (History)
CC List:	6 users (show)

See Also:
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?:	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.114
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016082621000083
Bug group (optional):
Max CVSS v3 score:

Attachments
patch (1.26 KB, patch) 2016-10-20 12:36 CEST, Florian Best	Details \| Diff
patch (1.93 KB, patch) 2016-10-20 12:49 CEST, Florian Best	Details \| Diff
Show Obsolete (1) View All 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 Michael Grandjean

2016-09-07 17:14:26 CEST

If the UCS Master is not reachable, the login to the UMC on a school server takes a very long time (~ 45 seconds in my case). If the Master becomes reachable again, it only takes about 2-3 seconds.

Reproducible in my test env.

Network master: 10.200.30.0/24
Network school: 10.200.23.0/24
UMC is accessed via IP (not Hostname/FQDN, no SSO), login as Administrator
UCS 4.1-3 errata 239
UCS@school 4.1 R2 v4

Comment 1 Michael Grandjean

2016-09-07 17:17:26 CEST

Also Ticket#2016082621000083

Comment 2 Jens Thorp-Hansen

2016-10-20 12:03:41 CEST

because of the environment this may gain severity quickly. Since the behaviour may happen generally in @school environments with a similar setting (bad connection between school sites and the master) and the UMC is a major administration tool in these environments I bumped the Bug-type to "5".

Comment 3 Sönke Schwardt-Krummrich

2016-10-20 12:25:53 CEST

Do we have any information that indicate the root cause of the problem?

Comment 4 Florian Best

2016-10-20 12:30:28 CEST

(In reply to Sönke Schwardt-Krummrich from comment #3)
> Do we have any information that indicate the root cause of the problem?
What do you mean with root cause?
1. Why the DC Master is not available
or 2. Why this is so slow

2. → PAM (the timeouts in each module of the pam stack)

Comment 5 Florian Best

2016-10-20 12:36:42 CEST

Created attachment 8139 [details]
patch

Ahh, no! I checked the whole UMC-Server code and got the problem. There is a ldap connection to the master - which is obviously wrong. Patch attached.

Comment 6 Florian Best

2016-10-20 12:49:47 CEST

Created attachment 8140 [details]
patch

Comment 7 Florian Best

2016-10-20 12:58:20 CEST

Introduced in Bug #38826 svn r62117

Comment 8 Florian Best

2016-11-08 18:58:40 CET

univention-management-console.yaml:
r74235 | YAML Bug #42310

univention-management-console (8.0.28-20):
r74234 | Bug #42310: don't connect to DC Master ldap on every UMC login attempt

Comment 9 Felix Botner

2016-11-15 12:52:35 CET

OK - UMC login with unreachable master
OK - YAML
OK - merged to 4.2-0

Comment 10 Janek Walkenhorst

2016-11-16 14:12:56 CET

<http://errata.software-univention.de/ucs/4.1/326.html>