Bug 37461 – AD-Member system setup should directly check time sync before starting the setup

Bug 37461 - AD-Member system setup should directly check time sync before starting the setup


Summary:	AD-Member system setup should directly check time sync before starting the setup

Status:	RESOLVED DUPLICATE of bug 36406

Product:	UCS
Classification:	Unclassified
Component:	UMC - Setup wizard
Version:	UCS 4.0
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-01-06 17:00 CET by Arvid Requate
Modified:	2015-01-08 07:03 CET (History)
CC List:	1 user (show)

See Also:
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:

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 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 ***