Bug 37461

Summary:	AD-Member system setup should directly check time sync before starting the setup
Product:	UCS	Reporter:	Arvid Requate <requate>
Component:	UMC - Setup wizard	Assignee:	UMC maintainers <umc-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	P5	CC:	gohmann
Version:	UCS 4.0
Target Milestone:	---
Hardware:	Other
OS:	Linux
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:

Description Arvid Requate

2015-01-06 17:00:14 CET

I just had the case where the AD-Member finally failed with a message explaining that the clock of the AD-Server was behind the clock of the local UCS system by more than 5 minutes. In that case the admember code refuses to revert the time to avoid certificate validity isues.

The system setup code should directly check the time synchronization of the UCS system against the AD-Server. Since the certificatzes are not even created at that point it would be even possible to directly synchronize the UCS clock to the AD-Server clock.

Comment 1 Stefan Gohmann

2015-01-08 07:03:21 CET


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