Bug 1904000
| Summary: | Force NTP sync against configured server on Ironic discovery | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Pablo Iranzo Gómez <pablo.iranzo> | ||||||
| Component: | Installer | Assignee: | Beth White <beth.white> | ||||||
| Installer sub component: | OpenShift on Bare Metal IPI | QA Contact: | Amit Ugol <augol> | ||||||
| Status: | CLOSED NOTABUG | Docs Contact: | |||||||
| Severity: | high | ||||||||
| Priority: | high | Keywords: | Triaged | ||||||
| Version: | 4.7 | ||||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.7.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-12-09 14:28:31 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: | 1831748 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1736035 [details]
time in the system BIOS
Setting clocks back to GMT with proper date and time, allows image to be written to disk, logs collected and system rebooting into CoreOS to continue/finish the installation on the three tested systems Sounds like an actual bug, not an RFE. Ironic has an option to synchronize time, we just need to make sure it runs earlier enough and we provide NTP server configuration. After talking to some folks internally and considering the options, I'm starting to agree that it's practically a new feature. We have a way to synchronize clocks in the agent, but no way to pass an NTP server (outside of machine configs). Since RFEs are tracked in Jira, could you create one in https://issues.redhat.com/projects/RFE/ please? Raised https://issues.redhat.com/browse/RFE-1471 on behalf of this |
Created attachment 1736034 [details] Traceback with failed SSL certificate Installer fails when NTP is not synced before installation, so there is a traceback with failed SSL certificate I've an environment deploying IPI 4.7 (4.7.0-0.nightly-2020-11-30-172451) but also failed with other releases (4.5, 4.6, etc). My configuration defines a NTP server, but I've deliberately set a wrong date in my workers. Each time the installer starts, even if NTP server is defined, Ironic fails to end-up the process because it doesn't sync the date/time *BEFORE* needing to check any SSL certificate (attached screenshoot from the remote console). Installer should set the time against he provided NTP server at first stage so that proper validation of certificates is performed even in the event of faulty batteries, etc.