Activity log for bug #1854694

Date Who What changed Old value New value Message
2019-12-02 07:26:43 Robert Liu bug added bug
2019-12-02 13:29:46 Robert Liu tags original-1853401
2019-12-03 02:15:12 Alex Kaluzhny bug added subscriber Michael Vogt
2019-12-03 02:15:23 Alex Kaluzhny bug added subscriber Zygmunt Krynicki
2019-12-03 10:48:07 Paweł Stołowski snapd: status New Triaged
2019-12-03 10:48:10 Paweł Stołowski snapd: importance Undecided High
2019-12-03 11:00:59 Paweł Stołowski snapd: importance High Medium
2019-12-03 11:01:11 Paweł Stołowski summary Watchdog settings don't be applied immediately Watchdog settings aren't applied immediately
2019-12-05 09:15:58 Samuele Pedroni snapd: assignee Samuele Pedroni (pedronis)
2019-12-19 10:53:47 Tiffany bug added subscriber Tiffany
2020-03-12 15:30:02 Michael Vogt snapd: importance Medium High
2020-03-13 04:32:19 Robert Liu description When setting/updating the watchdog configurations, the new configurations don't be applied immediately. Users should reboot the system or run 'systemctl daemon-reexec' manually to apply. When setting/updating the hardware watchdog timer through "snap set system watchdog.[runtime-timeout|shutdown-timeout]", the new configurations aren't applied immediately. Users should reboot the system or run 'systemctl daemon-reexec' manually to apply. "watchdog.[runtime-timeout|shutdown-timeout]" reflect to RuntimeWatchdogUSec and ShutdownWatchdogUSec of systemd-system.conf. Somehow, 'systemctl daemon-reload' doesn't reload the values.
2020-03-13 04:33:01 Robert Liu summary Watchdog settings aren't applied immediately "snap set system watchdog.*" settings aren't applied immediately
2020-04-06 11:36:38 Samuele Pedroni snapd: status Triaged In Progress
2020-06-22 09:29:18 Samuele Pedroni snapd: status In Progress Fix Committed
2020-06-23 11:39:48 Zygmunt Krynicki snapd: milestone 2.46
2020-11-30 10:00:54 Michael Vogt snapd: status Fix Committed Fix Released