| 2019-10-22 06:59:14 |
bugproxy |
bug |
|
|
added bug |
| 2019-10-22 06:59:17 |
bugproxy |
tags |
|
architecture-s39064 bugnameltc-182011 severity-high targetmilestone-inin1804 |
|
| 2019-10-22 06:59:18 |
bugproxy |
ubuntu: assignee |
|
Skipper Bug Screeners (skipper-screen-team) |
|
| 2019-10-22 06:59:22 |
bugproxy |
affects |
ubuntu |
systemd (Ubuntu) |
|
| 2019-10-22 07:02:58 |
Frank Heimes |
bug task added |
|
ubuntu-z-systems |
|
| 2019-10-22 07:03:20 |
Frank Heimes |
ubuntu-z-systems: importance |
Undecided |
High |
|
| 2019-10-22 07:03:38 |
Frank Heimes |
ubuntu-z-systems: assignee |
|
Canonical Foundations Team (canonical-foundations) |
|
| 2019-10-22 10:04:35 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2019-10-22 10:18:29 |
Dimitri John Ledkov |
bug watch added |
|
https://github.com/systemd/systemd/issues/8398 |
|
| 2019-10-22 10:32:04 |
Balint Reczey |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-10-22 10:32:04 |
Balint Reczey |
bug task added |
|
systemd (Ubuntu Eoan) |
|
| 2019-10-22 10:32:04 |
Balint Reczey |
nominated for series |
|
Ubuntu Disco |
|
| 2019-10-22 10:32:04 |
Balint Reczey |
bug task added |
|
systemd (Ubuntu Disco) |
|
| 2019-10-22 10:32:04 |
Balint Reczey |
nominated for series |
|
Ubuntu Bionic |
|
| 2019-10-22 10:32:04 |
Balint Reczey |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2019-10-22 10:32:26 |
Balint Reczey |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2019-10-22 10:32:55 |
Balint Reczey |
systemd (Ubuntu Eoan): status |
New |
Fix Released |
|
| 2019-10-22 10:33:02 |
Balint Reczey |
systemd (Ubuntu Disco): status |
New |
Fix Released |
|
| 2019-10-22 15:35:10 |
Steve Langasek |
summary |
Update systemd for ubuntu 18.04 with requested fix. |
Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart= |
|
| 2019-10-22 15:35:28 |
Steve Langasek |
description |
Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el s390x is available,
version 238 contains 9298 commits
version 239 contains 7690 commits
version 240 contains 4081 commits
The pull request for 240 is now requested to backport to 237 for Ubuntu 18.04, which is integrated within the IBM product.
Pull request: https://github.com/systemd/systemd/pull/9158 |
Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el s390x is available,
The pull request for 240 is now requested to backport to 237 for Ubuntu 18.04, which is integrated within the IBM product.
Pull request: https://github.com/systemd/systemd/pull/9158 |
|
| 2019-10-28 07:12:09 |
Frank Heimes |
ubuntu-z-systems: status |
New |
Triaged |
|
| 2019-12-06 18:27:37 |
Dan Streetman |
systemd (Ubuntu Bionic): status |
New |
In Progress |
|
| 2019-12-06 18:27:39 |
Dan Streetman |
systemd (Ubuntu Bionic): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-12-06 18:27:42 |
Dan Streetman |
systemd (Ubuntu Bionic): importance |
Undecided |
Medium |
|
| 2019-12-06 18:27:50 |
Dan Streetman |
tags |
architecture-s39064 bugnameltc-182011 severity-high targetmilestone-inin1804 |
architecture-s39064 bionic bugnameltc-182011 ddstreet severity-high systemd targetmilestone-inin1804 |
|
| 2019-12-06 18:49:02 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2019-12-13 01:45:52 |
Dan Streetman |
description |
Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el s390x is available,
The pull request for 240 is now requested to backport to 237 for Ubuntu 18.04, which is integrated within the IBM product.
Pull request: https://github.com/systemd/systemd/pull/9158 |
[impact]
services configured with both OnFailure= and Restart= directives will both start the failure service(s), as well as restarting itself. The documentation (and later versions) indicate that OnFailure= services will only be started once the service actually does stop (due to failure) once its restart limit has been exceeded.
[test case]
create service files as:
ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service
[Unit]
OnFailure=failure.service
[Service]
ExecStart=/bin/sh -c '/bin/sleep 10; /bin/false'
Restart=always
ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service
[Service]
ExecStart=/bin/true
perform daemon-reload, and then start test service:
ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload
ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl start test
wait for a while for the test service to exit - at least 10 seconds, as that's what we configured in the service, although I have waited longer in this example. Then check the journal for both test and failure services:
ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u test
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:18:34 UTC. --
Dec 13 01:17:43 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 1.
Dec 13 01:17:53 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:17:53 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 2.
Dec 13 01:18:04 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:04 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 3.
Dec 13 01:18:14 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 4.
Dec 13 01:18:24 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 5.
Dec 13 01:18:34 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: Started test.service.
ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u failure
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:19:15 UTC. --
Dec 13 01:17:53 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:03 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:44 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:55 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:19:05 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:19:15 lp1849261-b systemd[1]: Started failure.service.
note that the 'failure' service should not have been started at all.
[regression potential]
this changes how service failures are handled, specifically when OnFailure= services are started. However, this changes the behavior to be in line with the documentation, and the current behavior is unlikely to be anyone's desired behavior - both starting the failure service *and* restarting the failed service. However, this will cause a regression for anyone *expecting* both the OnFailure= service(s) to be started, as well as the failing service to be restarted.
Any other regression would likely occur during the state change of a unit, most likely during stop/exit of a service.
[scope]
This is needed only for Bionic and Xenial.
The patches to fix this:
7f66b026bbdda6bd3ddf7f617bf2c3a475e4a665
2ad2e41a72ec19159c0746a78e15ff880fe32a63
are included already in Disco and later.
[other info]
original description:
---
Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el s390x is available,
The pull request for 240 is now requested to backport to 237 for Ubuntu 18.04, which is integrated within the IBM product.
Pull request: https://github.com/systemd/systemd/pull/9158 |
|
| 2019-12-13 01:46:05 |
Dan Streetman |
nominated for series |
|
Ubuntu Xenial |
|
| 2019-12-13 01:46:05 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Xenial) |
|
| 2019-12-13 01:46:14 |
Dan Streetman |
systemd (Ubuntu Xenial): status |
New |
In Progress |
|
| 2019-12-13 01:46:17 |
Dan Streetman |
systemd (Ubuntu Xenial): assignee |
|
Dan Streetman (ddstreet) |
|
| 2019-12-13 01:46:18 |
Dan Streetman |
systemd (Ubuntu Xenial): importance |
Undecided |
Medium |
|
| 2019-12-13 01:46:29 |
Dan Streetman |
tags |
architecture-s39064 bionic bugnameltc-182011 ddstreet severity-high systemd targetmilestone-inin1804 |
architecture-s39064 bionic bugnameltc-182011 ddstreet severity-high systemd targetmilestone-inin1804 xenial |
|
| 2019-12-13 17:10:28 |
Dan Streetman |
description |
[impact]
services configured with both OnFailure= and Restart= directives will both start the failure service(s), as well as restarting itself. The documentation (and later versions) indicate that OnFailure= services will only be started once the service actually does stop (due to failure) once its restart limit has been exceeded.
[test case]
create service files as:
ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service
[Unit]
OnFailure=failure.service
[Service]
ExecStart=/bin/sh -c '/bin/sleep 10; /bin/false'
Restart=always
ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service
[Service]
ExecStart=/bin/true
perform daemon-reload, and then start test service:
ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload
ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl start test
wait for a while for the test service to exit - at least 10 seconds, as that's what we configured in the service, although I have waited longer in this example. Then check the journal for both test and failure services:
ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u test
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:18:34 UTC. --
Dec 13 01:17:43 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 1.
Dec 13 01:17:53 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:17:53 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 2.
Dec 13 01:18:04 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:04 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 3.
Dec 13 01:18:14 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 4.
Dec 13 01:18:24 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 5.
Dec 13 01:18:34 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: Started test.service.
ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u failure
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:19:15 UTC. --
Dec 13 01:17:53 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:03 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:44 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:55 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:19:05 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:19:15 lp1849261-b systemd[1]: Started failure.service.
note that the 'failure' service should not have been started at all.
[regression potential]
this changes how service failures are handled, specifically when OnFailure= services are started. However, this changes the behavior to be in line with the documentation, and the current behavior is unlikely to be anyone's desired behavior - both starting the failure service *and* restarting the failed service. However, this will cause a regression for anyone *expecting* both the OnFailure= service(s) to be started, as well as the failing service to be restarted.
Any other regression would likely occur during the state change of a unit, most likely during stop/exit of a service.
[scope]
This is needed only for Bionic and Xenial.
The patches to fix this:
7f66b026bbdda6bd3ddf7f617bf2c3a475e4a665
2ad2e41a72ec19159c0746a78e15ff880fe32a63
are included already in Disco and later.
[other info]
original description:
---
Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el s390x is available,
The pull request for 240 is now requested to backport to 237 for Ubuntu 18.04, which is integrated within the IBM product.
Pull request: https://github.com/systemd/systemd/pull/9158 |
[impact]
services configured with both OnFailure= and Restart= directives will both start the failure service(s), as well as restarting itself. The documentation (and later versions) indicate that OnFailure= services will only be started once the service actually does stop (due to failure) once its restart limit has been exceeded.
[test case]
create service files as:
ubuntu@lp1849261-b:/etc/systemd/system$ cat test.service
[Unit]
OnFailure=failure.service
[Service]
ExecStart=/bin/sh -c '/bin/sleep 10; /bin/false'
Restart=always
ubuntu@lp1849261-b:/etc/systemd/system$ cat failure.service
[Service]
ExecStart=/bin/true
perform daemon-reload, and then start test service:
ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl daemon-reload
ubuntu@lp1849261-b:/etc/systemd/system$ sudo systemctl start test
wait for a while for the test service to exit - at least 10 seconds, as that's what we configured in the service, although I have waited longer in this example. Then check the journal for both test and failure services:
ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u test
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:18:34 UTC. --
Dec 13 01:17:43 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:17:53 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 1.
Dec 13 01:17:53 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:17:53 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:03 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:04 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 2.
Dec 13 01:18:04 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:04 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:14 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 3.
Dec 13 01:18:14 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:24 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 4.
Dec 13 01:18:24 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: Started test.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Main process exited, code=exited, status=1/FAILURE
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Failed with result 'exit-code'.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Triggering OnFailure= dependencies.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Service hold-off time over, scheduling restart.
Dec 13 01:18:34 lp1849261-b systemd[1]: test.service: Scheduled restart job, restart counter is at 5.
Dec 13 01:18:34 lp1849261-b systemd[1]: Stopped test.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: Started test.service.
ubuntu@lp1849261-b:/etc/systemd/system$ journalctl -b -u failure
-- Logs begin at Fri 2019-12-13 00:52:50 UTC, end at Fri 2019-12-13 01:19:15 UTC. --
Dec 13 01:17:53 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:03 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:14 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:24 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:34 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:44 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:18:55 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:19:05 lp1849261-b systemd[1]: Started failure.service.
Dec 13 01:19:15 lp1849261-b systemd[1]: Started failure.service.
note that the 'failure' service should not have been started at all.
[regression potential]
this changes how service failures are handled, specifically when OnFailure= services are started. However, this changes the behavior to be in line with the documentation, and the current behavior is unlikely to be anyone's desired behavior - both starting the failure service *and* restarting the failed service. However, this will cause a regression for anyone *expecting* both the OnFailure= service(s) to be started, as well as the failing service to be restarted.
Any other regression would likely occur during the state change of a unit, most likely during stop/exit of a service.
[scope]
This is needed only for Bionic and Xenial (but marking WontFix for Xenial).
The patches to fix this:
7f66b026bbdda6bd3ddf7f617bf2c3a475e4a665
2ad2e41a72ec19159c0746a78e15ff880fe32a63
are included already in Disco and later.
For Xenial, I'm marking this as WontFix because it has additional backporting requirements; at least commit deb4e7080db and possibly more. Without anyone specifically requesting this for Xenial, I think the possibility for regression in Xenial due to the larger backport is too high to proactively apply it.
[other info]
original description:
---
Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el s390x is available,
The pull request for 240 is now requested to backport to 237 for Ubuntu 18.04, which is integrated within the IBM product.
Pull request: https://github.com/systemd/systemd/pull/9158 |
|
| 2019-12-13 17:10:37 |
Dan Streetman |
tags |
architecture-s39064 bionic bugnameltc-182011 ddstreet severity-high systemd targetmilestone-inin1804 xenial |
architecture-s39064 bionic bugnameltc-182011 ddstreet severity-high systemd targetmilestone-inin1804 |
|
| 2019-12-13 17:10:44 |
Dan Streetman |
systemd (Ubuntu Xenial): status |
In Progress |
Won't Fix |
|
| 2019-12-13 17:10:50 |
Dan Streetman |
systemd (Ubuntu Xenial): assignee |
Dan Streetman (ddstreet) |
|
|
| 2019-12-20 19:25:16 |
Francis Ginther |
tags |
architecture-s39064 bionic bugnameltc-182011 ddstreet severity-high systemd targetmilestone-inin1804 |
architecture-s39064 bionic bugnameltc-182011 ddstreet id-5de127a738dabd05006e38e8 severity-high systemd targetmilestone-inin1804 |
|
| 2020-01-20 09:31:28 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
In Progress |
Triaged |
|
| 2020-01-20 09:31:31 |
Dimitri John Ledkov |
ubuntu-z-systems: status |
In Progress |
Triaged |
|
| 2020-01-20 12:43:49 |
Dan Streetman |
systemd (Ubuntu Bionic): status |
Triaged |
In Progress |
|
| 2020-01-20 12:51:40 |
Frank Heimes |
ubuntu-z-systems: status |
Triaged |
In Progress |
|
| 2020-02-03 21:54:52 |
Steve Langasek |
systemd (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-02-03 21:54:57 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-02-03 21:54:59 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2020-02-03 21:55:06 |
Steve Langasek |
tags |
architecture-s39064 bionic bugnameltc-182011 ddstreet id-5de127a738dabd05006e38e8 severity-high systemd targetmilestone-inin1804 |
architecture-s39064 bionic bugnameltc-182011 ddstreet id-5de127a738dabd05006e38e8 severity-high systemd targetmilestone-inin1804 verification-needed verification-needed-bionic |
|
| 2020-02-04 05:22:43 |
Frank Heimes |
ubuntu-z-systems: status |
In Progress |
Fix Committed |
|
| 2020-02-06 15:22:31 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
Fix Committed |
In Progress |
|
| 2020-02-06 21:47:56 |
Steve Langasek |
systemd (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-02-16 14:44:56 |
Dan Streetman |
tags |
architecture-s39064 bionic bugnameltc-182011 ddstreet id-5de127a738dabd05006e38e8 severity-high systemd targetmilestone-inin1804 verification-needed verification-needed-bionic |
architecture-s39064 bionic bugnameltc-182011 ddstreet id-5de127a738dabd05006e38e8 severity-high systemd targetmilestone-inin1804 verification-done verification-done-bionic |
|
| 2020-02-17 09:58:01 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-02-17 10:07:54 |
Launchpad Janitor |
systemd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-02-17 10:16:39 |
Frank Heimes |
ubuntu-z-systems: status |
Fix Committed |
Fix Released |
|
