Loading...

XML

Word

Printable

Severity:
Important
Regression:
No
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
{ztp} provides an additional script during the startup of {sno} clusters provisioning. To mitigate the impact of malfunctioning BIOS clocks, the script sets the {sno} cluster clock once through the NTP (Network Time Protocol) server before the {sno} cluster clock is synchronized through PTP (Precision Time Protocol).

Show
{ztp} provides an additional script during the startup of {sno} clusters provisioning. To mitigate the impact of malfunctioning BIOS clocks, the script sets the {sno} cluster clock once through the NTP (Network Time Protocol) server before the {sno} cluster clock is synchronized through PTP (Precision Time Protocol).
Release Note Type:
Bug Fix
Release Note Status:
Done
RH Private Keywords:
Target Version:

4.12.z
Target Backport Versions:

4.12.z

This is a clone of issue OCPBUGS-33349. The following is the description of the original issue:
—
Description of problem:

RT clock on a customer's system provided incorrect time on boot; The fix in https://github.com/openshift-kni/cnf-features-deploy/pull/1438/commits (which was introduced in 4.14) would have mitigated this issue properly.

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

4.12

How reproducible:

Infrequent

Steps to Reproduce:

    1. Multiple reboots occur
    2. Kernel reads a wrong date from the RTC and sets the system time to 30 years in the future
    3.

Actual results:

System gets the wrong time and fails to come up fully due to certificate errors

Expected results:

The time is set properly and the system recovers fully.

Additional info:

clones

OCPBUGS-33349 Customers on 4.12 need the "one-shot time sync on boot" fix from 4.14

is blocked by

OCPBUGS-33349 Customers on 4.12 need the "one-shot time sync on boot" fix from 4.14

links to

RHEA-2024:128710 OpenShift Container Platform 4.12.8 CNF vRAN extras update

mentioned on

(1 mentioned on)