Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1809063

Summary:	[Bare metal] Installation on a network restricted environment with clock out of sync
Product:	OpenShift Container Platform	Reporter:	Mario Abajo <mabajodu>
Component:	RHCOS	Assignee:	Colin Walters <walters>
Status:	CLOSED DUPLICATE	QA Contact:	Michael Nguyen <mnguyen>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.3.z	CC:	bbreard, dornelas, dustymabe, imcleod, jligon, miabbott, nstielau, smilner
Target Milestone:	---
Target Release:	4.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-10 19:04:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1186913

Description Mario Abajo 2020-03-02 11:29:38 UTC

Description of problem:
- Premise:
  * Installation on a network restricted environment
  * bare metal hardware with the clock out of sync (with respect to UTC)

- Result:
  * chronyd default config cannot access public defined ntp sources
  * with the clock out of sync the certificates will be invalid (by date)
  * installation delays (in case of minutes deviation) or fail (worst scenario)

- Workaround:
  * modify ignition files to add personalized chronyd configuration to access internal ntp
  __OR__
  * manually modify the clock of the system/s
  * create a machineconfig to set chronyd configuration

Version-Release number of selected component (if applicable):
OCP 4.3.0

How reproducible:
Always

Steps to Reproduce:
1. 
2.
3.

Actual results:
Installation delays / fail

Expected results:
Kernel parameter to add NTP servers or an advise in the documentation stating to take care of the date/time of the systems prior to installing it.


Additional info:

Comment 1 Micah Abbott 2020-03-04 03:08:19 UTC

This reads like more support for a time servers section in the MachineConfig or install-config.yaml

See also https://github.com/openshift/machine-config-operator/issues/629

Comment 2 Mario Abajo 2020-03-05 09:30:27 UTC

Yes, thanks, an install-config.yaml + MachineConfig will address the issue perfectly.

Comment 5 Colin Walters 2020-06-10 19:04:12 UTC

We have another bug which is likely covering what you want here.

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