Bug 36406

Summary: Join into AD: Clock synchronization
Product: UCS Reporter: Stefan Gohmann <gohmann>
Component: System setupAssignee: Arvid Requate <requate>
Status: CLOSED FIXED QA Contact: Stefan Gohmann <gohmann>
Severity: normal    
Priority: P5 CC: requate, walkenhorst
Version: UCS 3.2   
Target Milestone: UCS 4.0-0-errata   
Hardware: Other   
OS: Linux   
See Also: https://forge.univention.org/bugzilla/show_bug.cgi?id=36413
What kind of report is it?: --- What type of bug is this?: ---
Who will be affected by this bug?: --- How will those affected feel about the bug?: ---
User Pain: Enterprise Customer affected?:
School Customer affected?: ISV affected?:
Waiting Support: Flags outvoted (downgraded) after PO Review:
Ticket number: Bug group (optional):
Max CVSS v3 score:
Bug Depends on: 37481    
Bug Blocks: 37482    

Description Stefan Gohmann univentionstaff 2014-11-03 21:24:37 CET
Currently, the installation failed if the AD clock is more than 360 seconds behind the local clock. I think during the installation the clock should be synced in any case.
Comment 1 Stefan Gohmann univentionstaff 2015-01-08 07:03:21 CET
*** Bug 37461 has been marked as a duplicate of this bug. ***
Comment 2 Arvid Requate univentionstaff 2015-01-08 13:51:25 CET
Note: Depends on univention-lib erratum Bug #37481
Advisory: 2014-12-09-univention-system-setup.yaml
Tests: via Bug #37482
Comment 3 Stefan Gohmann univentionstaff 2015-01-21 07:12:28 CET
The installation still fails with the message that the AD time is more than 360 seconds behind the local clock. I think it is important that we use the AD system already as time server before the SSL infrastructure is created.
Comment 4 Arvid Requate univentionstaff 2015-01-21 23:44:16 CET
Ok, adjusted. A try/except was still missing at a later point.
Advisory updated.
Comment 5 Stefan Gohmann univentionstaff 2015-01-22 07:10:14 CET
OK, the installation works now.
Comment 6 Janek Walkenhorst univentionstaff 2015-01-29 11:43:40 CET
<http://errata.univention.de/ucs/4.0/57.html>