[systemd-bugs] [Bug 58216] New: if "systemctl daemon-reload" is executed right before timer expires, timer doesn't fire nor rearm

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=58216

          Priority: medium
            Bug ID: 58216
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: if "systemctl daemon-reload" is executed right before
                    timer expires, timer doesn't fire nor rearm
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: Alex.Jones at genband.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Created attachment 71415
  --> https://bugs.freedesktop.org/attachment.cgi?id=71415&action=edit
gzipped tar file containing files needed to reproduce the bug

If "systemctl daemon-reload" is executed within a second of a timer expiring,
the timer will not fire and will never be rearmed.  It stays in "elapsed" state
forever.

I originally see this problem in OpenSUSE-12.1 which uses systemd-37, but I
have tested this against the stock systemd-196, and the problem still exists
there.

I've included a gzipped tarfile which contains a service file
(elapsed-bug.service), a timer file (elapsed-service.timer), and a bash script
which reproduces the bug.

How to reproduce the bug:

1) install the service and timer file in /etc/systemd/system
2) modify ExecStart in the service file to log something to a file or something
of that nature (so you know the timer is running properly)
3) systemctl daemon-reload
4) systemctl enable elapsed-bug.timer
5) systemctl start elapsed-bug.timer
6) make sure the timer is running properly
7) run test1.sh (you may need to modify the awk field depending on the output
of "systemctl status elapsed-bug.service")
8) it will print out a message that it has found the bug, and then exit (may
take a minute or two)
9) verify that your printout (or whatever your ExecStart was doing) is no
longer doing it

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20121212/7e2cddc9/attachment.html>