Bug 1135600

Summary: [RFE] Backport systemd 216 timer-sync.target changes for OnCalendar
Product: Red Hat Enterprise Linux 7 Reporter: Pat Riehecky <riehecky>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Branislav Blaškovič <bblaskov>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: bblaskov, jscotka, lnykryn, systemd-maint-list
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-219-1.el7 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-19 14:57:23 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:

Description Pat Riehecky 2014-08-29 18:28:07 UTC
Description of problem: From the ssytemd 216 announcement:

        * timer units with at least one OnCalendar= setting will now
          be started only after timer-sync.target has been
          reached. This way they will not elapse before the system
          clock has been corrected by a local NTP client or
          similar. This is particular useful on RTC-less embedded
          machines, that come up with an invalid system clock.

Several of my existing systems have very unstable local clocks.  I believe this fix would help keep my timer based units executing as I expect.

Version-Release number of selected component (if applicable):systemd-208-11.el7_0.2


How reproducible:
100%

Steps to Reproduce:
1.Find a system with a dead CMOS battery, boot it with several timer units using OnCalendar
2.
3.

Actual results:
Strange, and somewhat unknown behavior

Expected results:
timer based units wait until after time sync successful

Additional info:

Comment 4 Lukáš Nykrýn 2015-04-21 13:51:07 UTC
This should be now fixed with the rebase.

Comment 6 Branislav Blaškovič 2015-09-07 11:12:14 UTC
systemd was rebased to version 219.
Marking as VERIFIED SanityOnly.

Comment 7 errata-xmlrpc 2015-11-19 14:57:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2092.html