# VERIFICATION QUESTING

Installed systemd package from -proposed:

# dpkg -l | grep systemd

dbus-user-session         1.16.2-2ubuntu2      amd64         simple 
interprocess messaging system (systemd --user integration)
libnss-systemd:amd64      257.9-0ubuntu2.4     amd64         nss module 
providing dynamic user and group name resolution
libpam-systemd:amd64      257.9-0ubuntu2.4     amd64         system and service 
manager - PAM module
libsystemd-shared:amd64   257.9-0ubuntu2.4     amd64         systemd shared 
private library
libsystemd0:amd64         257.9-0ubuntu2.4     amd64         systemd utility 
library
networkd-dispatcher       2.2.4-1.1            all           Dispatcher service 
for systemd-networkd connection status changes
python3-systemd           235-1build6          amd64         Python 3 bindings 
for systemd
systemd                   257.9-0ubuntu2.4     amd64         system and service 
manager
systemd-cryptsetup        257.9-0ubuntu2.4     amd64         Provides 
cryptsetup, integritysetup and veritysetup utilities
systemd-hwe-hwdb          257.7.2              all           udev rules for 
hardware enablement (HWE)
systemd-resolved          257.9-0ubuntu2.4     amd64         systemd DNS 
resolver
systemd-sysv              257.9-0ubuntu2.4     amd64         system and service 
manager - SysV compatibility symlinks


Followed the test plan from the description:

1. Create a service and a timer.

# timer-test.service

[Unit]
Description="Test service"

[Service]
ExecStart=/bin/echo triggered
Type=oneshot

# timer-test.timer

[Unit]
Description="Test timer"

[Timer]
OnCalendar=*-*-* *:17:00

[Install]
WantedBy=timers.target


2. Enable the timer.

# sudo systemctl enable --now timer-test.timer


3. Let the timer trigger once.

This is important because you don't see this behavior if the timer has
never ran before.


4. Restart the timer:

# systemctl restart timer-test.timer

Mar 26 16:18:18 questingcont systemd[1]: Stopped timer-test.timer - Test timer.
Mar 26 16:18:18 questingcont systemd[1]: Stopping timer-test.timer - Test 
timer...
Mar 26 16:18:18 questingcont systemd[1]: Started timer-test.timer - Test timer.


5. View the service status to see the logged echo command and check the time 
when the service was triggered.

# systemctl status timer-test.service

Mar 26 16:17:01 questingcont systemd[1]: Starting timer-test.service - Test 
service...
Mar 26 16:17:01 questingcont echo[4354]: triggered
Mar 26 16:17:01 questingcont systemd[1]: timer-test.service: Deactivated 
successfully.
Mar 26 16:17:01 questingcont systemd[1]: Finished timer-test.service - Test 
service.


The service triggered at 16:17 and the timer was restarted at 16:18.

This confirms that now the behaviour is correct. 
After restarting the timer, the service did not run again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2141296

Title:
  [00427578] Restarting systemd timer triggers service start off-
  schedule

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2141296/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to