| 2021-01-12 12:14:52 |
Ioanna Alifieraki |
bug |
|
|
added bug |
| 2021-01-12 12:15:25 |
Ioanna Alifieraki |
tags |
|
sts |
|
| 2021-01-12 12:15:35 |
Ioanna Alifieraki |
systemd (Ubuntu): status |
New |
Confirmed |
|
| 2021-01-12 12:15:38 |
Ioanna Alifieraki |
systemd (Ubuntu): importance |
Undecided |
Medium |
|
| 2021-01-12 12:15:41 |
Ioanna Alifieraki |
systemd (Ubuntu): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2021-01-12 12:25:40 |
Ioanna Alifieraki |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
The patch has minimal regression potential since it just takes no action ( instead of shutting down ) when bus_call_method fails.
[OTHER]
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
The patch has minimal regression potential since it just takes no action ( instead of shutting down ) when bus_call_method fails.
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-01-14 15:22:35 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2021-01-14 17:36:17 |
Ioanna Alifieraki |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
The patch has minimal regression potential since it just takes no action ( instead of shutting down ) when bus_call_method fails.
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-01-19 13:03:04 |
Balint Reczey |
systemd (Ubuntu): status |
Confirmed |
In Progress |
|
| 2021-01-19 13:03:21 |
Balint Reczey |
systemd (Ubuntu): status |
In Progress |
Confirmed |
|
| 2021-02-23 13:17:34 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Focal |
|
| 2021-02-23 13:17:34 |
Ioanna Alifieraki |
bug task added |
|
systemd (Ubuntu Focal) |
|
| 2021-02-23 13:17:34 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Groovy |
|
| 2021-02-23 13:17:34 |
Ioanna Alifieraki |
bug task added |
|
systemd (Ubuntu Groovy) |
|
| 2021-02-23 13:17:34 |
Ioanna Alifieraki |
nominated for series |
|
Ubuntu Bionic |
|
| 2021-02-23 13:17:34 |
Ioanna Alifieraki |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2021-02-23 13:17:42 |
Ioanna Alifieraki |
systemd (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2021-02-23 13:17:44 |
Ioanna Alifieraki |
systemd (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2021-02-23 13:17:45 |
Ioanna Alifieraki |
systemd (Ubuntu Groovy): importance |
Undecided |
Medium |
|
| 2021-02-23 13:19:24 |
Ioanna Alifieraki |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[OTHER]
This is now fixed in H, currently affects B,G,F.
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-02-23 13:24:28 |
Ioanna Alifieraki |
attachment added |
|
lp1911187_bionic.debdiff https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+attachment/5466200/+files/lp1911187_bionic.debdiff |
|
| 2021-02-23 13:25:02 |
Ioanna Alifieraki |
attachment added |
|
lp1911187_groovy.debdiff https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+attachment/5466201/+files/lp1911187_groovy.debdiff |
|
| 2021-02-23 13:25:32 |
Ioanna Alifieraki |
attachment added |
|
lp1911187_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+attachment/5466202/+files/lp1911187_focal.debdiff |
|
| 2021-02-23 13:25:33 |
Ioanna Alifieraki |
attachment added |
|
lp1911187_focal.debdiff https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1911187/+attachment/5466203/+files/lp1911187_focal.debdiff |
|
| 2021-02-23 13:25:40 |
Ioanna Alifieraki |
systemd (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2021-02-23 13:25:42 |
Ioanna Alifieraki |
systemd (Ubuntu Focal): status |
New |
Confirmed |
|
| 2021-02-23 13:25:46 |
Ioanna Alifieraki |
systemd (Ubuntu Groovy): status |
New |
Confirmed |
|
| 2021-02-23 13:26:11 |
Ioanna Alifieraki |
tags |
sts |
sts sts-sponsors |
|
| 2021-02-23 13:26:33 |
Ioanna Alifieraki |
bug |
|
|
added subscriber STS Sponsors |
| 2021-02-23 13:36:34 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2021-02-23 13:39:38 |
Eric Desrochers |
tags |
sts sts-sponsors |
sts sts-sponsors sts-sponsors-ddstreet |
|
| 2021-02-23 13:40:10 |
Eric Desrochers |
systemd (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2021-02-23 13:40:12 |
Eric Desrochers |
systemd (Ubuntu Groovy): status |
Confirmed |
In Progress |
|
| 2021-02-23 13:40:14 |
Eric Desrochers |
systemd (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2021-02-23 13:40:23 |
Eric Desrochers |
systemd (Ubuntu Bionic): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2021-02-23 13:40:29 |
Eric Desrochers |
systemd (Ubuntu Focal): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2021-02-23 13:40:36 |
Dan Streetman |
systemd (Ubuntu Focal): assignee |
Ioanna Alifieraki (joalif) |
Dan Streetman (ddstreet) |
|
| 2021-02-23 13:40:38 |
Eric Desrochers |
systemd (Ubuntu Groovy): assignee |
|
Ioanna Alifieraki (joalif) |
|
| 2021-02-23 13:40:44 |
Dan Streetman |
systemd (Ubuntu Focal): assignee |
Dan Streetman (ddstreet) |
Ioanna Alifieraki (joalif) |
|
| 2021-02-23 13:44:21 |
Dan Streetman |
systemd (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2021-02-23 13:46:38 |
Ioanna Alifieraki |
tags |
sts sts-sponsors sts-sponsors-ddstreet |
sts sts-sponsors |
|
| 2021-02-23 13:49:41 |
Ioanna Alifieraki |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[OTHER]
This is now fixed in H, currently affects B,G,F.
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[SCOPE]
This is already in H, need backporting to B,G,F.
Ubuntu-hirsute commits :
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?
h=ubuntu-hirsute&id=ce31df6711a8e112cff929ed3bbdcd194f876270
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-hirsute&id=ec1130fece7ca66273773119775e51045a74122c
Debian commits :
https://salsa.debian.org/systemd-team/systemd/-/commit/ce31df6711a8e112cff929ed3bbdcd194f876270
https://salsa.debian.org/systemd-team/systemd/-/commit/ec1130fece7ca66273773119775e51045a74122c
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-02-23 13:50:27 |
Ioanna Alifieraki |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[SCOPE]
This is already in H, need backporting to B,G,F.
Ubuntu-hirsute commits :
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?
h=ubuntu-hirsute&id=ce31df6711a8e112cff929ed3bbdcd194f876270
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-hirsute&id=ec1130fece7ca66273773119775e51045a74122c
Debian commits :
https://salsa.debian.org/systemd-team/systemd/-/commit/ce31df6711a8e112cff929ed3bbdcd194f876270
https://salsa.debian.org/systemd-team/systemd/-/commit/ec1130fece7ca66273773119775e51045a74122c
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[SCOPE]
This is already in H, need backporting to B,G,F.
Ubuntu-hirsute commits :
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-hirsute&id=ce31df6711a8e112cff929ed3bbdcd194f876270
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-hirsute&id=ec1130fece7ca66273773119775e51045a74122c
Debian commits :
https://salsa.debian.org/systemd-team/systemd/-/commit/ce31df6711a8e112cff929ed3bbdcd194f876270
https://salsa.debian.org/systemd-team/systemd/-/commit/ec1130fece7ca66273773119775e51045a74122c
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-02-23 13:53:39 |
Eric Desrochers |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST CASE]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[REGRESSION POTENTIAL]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[SCOPE]
This is already in H, need backporting to B,G,F.
Ubuntu-hirsute commits :
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-hirsute&id=ce31df6711a8e112cff929ed3bbdcd194f876270
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?h=ubuntu-hirsute&id=ec1130fece7ca66273773119775e51045a74122c
Debian commits :
https://salsa.debian.org/systemd-team/systemd/-/commit/ce31df6711a8e112cff929ed3bbdcd194f876270
https://salsa.debian.org/systemd-team/systemd/-/commit/ec1130fece7ca66273773119775e51045a74122c
[OTHER]
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST PLAN]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[WHERE PROBLEM COULD OCCUR]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[OTHER]
This is now fixed in H, currently affects B,G,F.
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-02-23 23:06:47 |
Dan Streetman |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST PLAN]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[WHERE PROBLEM COULD OCCUR]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it.
Other than that the changes in the code are very small and simple and unlikely to break anything.
[OTHER]
This is now fixed in H, currently affects B,G,F.
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST PLAN]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[WHERE PROBLEM COULD OCCUR]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error.
Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot.
[OTHER]
This is now fixed in H, currently affects B,G,F.
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-03-08 09:38:25 |
Łukasz Zemczak |
systemd (Ubuntu Groovy): status |
In Progress |
Fix Committed |
|
| 2021-03-08 09:38:26 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-03-08 09:38:28 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2021-03-08 09:38:32 |
Łukasz Zemczak |
tags |
sts sts-sponsors |
sts sts-sponsors verification-needed verification-needed-groovy |
|
| 2021-03-08 09:47:18 |
Łukasz Zemczak |
systemd (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-03-08 09:47:24 |
Łukasz Zemczak |
tags |
sts sts-sponsors verification-needed verification-needed-groovy |
sts sts-sponsors verification-needed verification-needed-focal verification-needed-groovy |
|
| 2021-03-08 09:53:27 |
Łukasz Zemczak |
systemd (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2021-03-08 09:53:32 |
Łukasz Zemczak |
tags |
sts sts-sponsors verification-needed verification-needed-focal verification-needed-groovy |
sts sts-sponsors verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy |
|
| 2021-03-11 14:07:28 |
Ioanna Alifieraki |
tags |
sts sts-sponsors verification-needed verification-needed-bionic verification-needed-focal verification-needed-groovy |
sts sts-sponsors verification-done-bionic verification-needed verification-needed-focal verification-needed-groovy |
|
| 2021-03-11 14:12:51 |
Ioanna Alifieraki |
tags |
sts sts-sponsors verification-done-bionic verification-needed verification-needed-focal verification-needed-groovy |
sts sts-sponsors verification-done-bionic verification-done-focal verification-needed verification-needed-groovy |
|
| 2021-03-11 14:27:33 |
Ioanna Alifieraki |
tags |
sts sts-sponsors verification-done-bionic verification-done-focal verification-needed verification-needed-groovy |
sts sts-sponsors verification-done verification-done-bionic verification-done-focal verification-done-groovy |
|
| 2021-03-11 15:39:02 |
Ioanna Alifieraki |
description |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST PLAN]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
[WHERE PROBLEM COULD OCCUR]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error.
Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot.
[OTHER]
This is now fixed in H, currently affects B,G,F.
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
[IMPACT]
When, for whatever reason, logind or dbus is not available scheduled reboot reboots the machine immediately.
From the sources it seems that this is intended :
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L318
However, I report this as a bug since this is against the logic of a scheduled reboot; if someone schedules a reboot they want the system to reboot at the specified time not immediately.
There has been a discussion upstream ( https://github.com/systemd/systemd/issues/17575 ) and
a PR ( https://github.com/systemd/systemd/pull/18010 ).
Upstream community is not willing to accept the patch but debian is.
I open this bug to to pull the patch into Ubuntu once it lands in debian.
[TEST PLAN]
The simpler reproducer is to disable dbus to imitate the real world case.
# systemctl stop dbus.service
# systemctl stop dbus.socket
# shutdown +1140 -r "REBOOT!"
Failed to set wall message, ignoring: Failed to activate service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)
Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Connection timed out
Connection to groovy closed by remote host.
Connection to groovy closed.
After this patch is applied the shutdown command does not reboot immediately if it fails to schedule the shutdown. Instead it does nothing
and returns a non zero return code that can be checked by calling scripts or users.
[WHERE PROBLEM COULD OCCUR]
This patch changes the behaviour of scheduled reboot in case logind or dbus has failed.
Originally, if logind is not available (call to logind bus fails
https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl-logind.c#L319)
it proceeds with immediate shutdown.
This patch changes this behaviour and instead of shutting down it does nothing.
The actual regression potential is a user asking for a reboot and not getting it, so the largest regression potential is any existing users (human or programmatic) that are requesting a scheduled shutdown but not checking the return value for error.
Any other regression would likely result in the system incorrectly not rebooted, or incorrectly scheduled for reboot.
[OTHER]
This is now fixed in H, currently affects B,G,F.
Debian bug reports :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931235
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960042
Upstream issue : https://github.com/systemd/systemd/issues/17575
PR : https://github.com/systemd/systemd/pull/18010 |
|
| 2021-03-18 12:29:34 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-03-18 12:39:33 |
Launchpad Janitor |
systemd (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2021-03-18 13:27:34 |
Launchpad Janitor |
systemd (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2021-03-18 13:52:29 |
Launchpad Janitor |
systemd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
