| 2018-12-03 21:17:33 |
errors.ubuntu.com bug bridge |
bug |
|
|
added bug |
| 2018-12-03 21:17:35 |
errors.ubuntu.com bug bridge |
bug |
|
|
added subscriber Balint Reczey |
| 2018-12-13 13:31:24 |
Balint Reczey |
description |
The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.7, the problem page at https://errors.ubuntu.com/problem/caf5d885046359f4857cee6c4a61e1d72d0913b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. |
[Impact]
* Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start.
* Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process.
* The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence.
[Test Case]
* Stop systemd-logind and make it unable to start for example by masking it:
root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service
root@bb-logind:~# rm /etc/systemd/system/systemd-logind
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service systemd-logind stop
root@bb-logind:~# service systemd-logind status
● systemd-logind.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago
Main PID: 1938 (code=killed, signal=TERM)
Status: "Processing requests..."
...
* Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start.
* Restore logind's ability to start
* Restart unattended-upgrades.service
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service unattended-upgrades restart
root@bb-logind:~# service unattended-upgrades status
● unattended-upgrades.service - Unattended Upgrades Shutdown
Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-12-13 13:08:13 UTC; 16s ago
Docs: man:unattended-upgrade(8)
Main PID: 2079 (unattended-upgr)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/unattended-upgrades.service
└─2079 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
Dec 13 13:08:13 bb-logind systemd[1]: Started Unattended Upgrades Shutdown.
root@bb-logind:~# systemd-analyze dot | grep unattended
...
"unattended-upgrades.service"->"systemd-logind.service" [color="green"];
...
[Regression Potential]
* The change to service ordering is unlikely to cause any issue, but the graceful handling of missing logind involved a small-scale refactoring of u-u-s's code. Extensive testing did not reveal regressions in that area, but potential bugs may cause u-u.service fail to start and affect graceful shutdown of u-u the same way as detailed in [Impact].
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.7, the problem page at https://errors.ubuntu.com/problem/caf5d885046359f4857cee6c4a61e1d72d0913b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. |
|
| 2018-12-13 13:32:50 |
Balint Reczey |
unattended-upgrades (Ubuntu): importance |
Undecided |
Critical |
|
| 2018-12-13 13:36:59 |
Balint Reczey |
description |
[Impact]
* Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start.
* Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process.
* The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence.
[Test Case]
* Stop systemd-logind and make it unable to start for example by masking it:
root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service
root@bb-logind:~# rm /etc/systemd/system/systemd-logind
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service systemd-logind stop
root@bb-logind:~# service systemd-logind status
● systemd-logind.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago
Main PID: 1938 (code=killed, signal=TERM)
Status: "Processing requests..."
...
* Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start.
* Restore logind's ability to start
* Restart unattended-upgrades.service
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service unattended-upgrades restart
root@bb-logind:~# service unattended-upgrades status
● unattended-upgrades.service - Unattended Upgrades Shutdown
Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-12-13 13:08:13 UTC; 16s ago
Docs: man:unattended-upgrade(8)
Main PID: 2079 (unattended-upgr)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/unattended-upgrades.service
└─2079 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
Dec 13 13:08:13 bb-logind systemd[1]: Started Unattended Upgrades Shutdown.
root@bb-logind:~# systemd-analyze dot | grep unattended
...
"unattended-upgrades.service"->"systemd-logind.service" [color="green"];
...
[Regression Potential]
* The change to service ordering is unlikely to cause any issue, but the graceful handling of missing logind involved a small-scale refactoring of u-u-s's code. Extensive testing did not reveal regressions in that area, but potential bugs may cause u-u.service fail to start and affect graceful shutdown of u-u the same way as detailed in [Impact].
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.7, the problem page at https://errors.ubuntu.com/problem/caf5d885046359f4857cee6c4a61e1d72d0913b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. |
[Impact]
* Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start.
* Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process.
* The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence.
[Test Case]
* Stop systemd-logind and make it unable to start for example by masking it:
root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service
root@bb-logind:~# rm /etc/systemd/system/systemd-logind
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service systemd-logind stop
root@bb-logind:~# service systemd-logind status
● systemd-logind.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago
Main PID: 1938 (code=killed, signal=TERM)
Status: "Processing requests..."
...
* Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start.
* Restore logind's ability to start
* Restart unattended-upgrades.service
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service unattended-upgrades restart
root@bb-logind:~# service unattended-upgrades status
● unattended-upgrades.service - Unattended Upgrades Shutdown
Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-12-13 13:08:13 UTC; 16s ago
Docs: man:unattended-upgrade(8)
Main PID: 2079 (unattended-upgr)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/unattended-upgrades.service
└─2079 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
Dec 13 13:08:13 bb-logind systemd[1]: Started Unattended Upgrades Shutdown.
root@bb-logind:~# systemd-analyze dot | grep unattended
...
"unattended-upgrades.service"->"systemd-logind.service" [color="green"];
...
[Regression Potential]
* The change to service ordering is unlikely to cause any issue, but the graceful handling of missing logind involved a small-scale refactoring of u-u-s's code. Extensive testing did not reveal regressions in that area, but potential bugs may cause u-u.service fail to start and affect graceful shutdown of u-u the same way as detailed in [Impact].
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.7, the problem page at https://errors.ubuntu.com/problem/caf5d885046359f4857cee6c4a61e1d72d0913b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.
Also seen as:
* https://errors.ubuntu.com/problem/ac61b23e0ec25a291427b875bf213fdd5b097fa5 |
|
| 2018-12-13 14:34:09 |
Balint Reczey |
description |
[Impact]
* Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start.
* Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process.
* The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence.
[Test Case]
* Stop systemd-logind and make it unable to start for example by masking it:
root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service
root@bb-logind:~# rm /etc/systemd/system/systemd-logind
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service systemd-logind stop
root@bb-logind:~# service systemd-logind status
● systemd-logind.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago
Main PID: 1938 (code=killed, signal=TERM)
Status: "Processing requests..."
...
* Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start.
* Restore logind's ability to start
* Restart unattended-upgrades.service
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service unattended-upgrades restart
root@bb-logind:~# service unattended-upgrades status
● unattended-upgrades.service - Unattended Upgrades Shutdown
Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-12-13 13:08:13 UTC; 16s ago
Docs: man:unattended-upgrade(8)
Main PID: 2079 (unattended-upgr)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/unattended-upgrades.service
└─2079 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
Dec 13 13:08:13 bb-logind systemd[1]: Started Unattended Upgrades Shutdown.
root@bb-logind:~# systemd-analyze dot | grep unattended
...
"unattended-upgrades.service"->"systemd-logind.service" [color="green"];
...
[Regression Potential]
* The change to service ordering is unlikely to cause any issue, but the graceful handling of missing logind involved a small-scale refactoring of u-u-s's code. Extensive testing did not reveal regressions in that area, but potential bugs may cause u-u.service fail to start and affect graceful shutdown of u-u the same way as detailed in [Impact].
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.7, the problem page at https://errors.ubuntu.com/problem/caf5d885046359f4857cee6c4a61e1d72d0913b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.
Also seen as:
* https://errors.ubuntu.com/problem/ac61b23e0ec25a291427b875bf213fdd5b097fa5 |
[Impact]
* Unattended-upgrades.service may crash due to starting earlier than dbus and logind are up or due to logind failing to start.
* Unattended-upgrades.service not starting prevents installation of upgrades on shutdown (when u-u is configured to do that) and also prevents gracefully stopping running u-u _before_ shutdown as implemented in LP: #1803137. U-u is still stopped gracefully after the shutdown transaction is started, but that may let service restarts hang the upgrade process.
* The fix is adding an After service dependency on systemd-logind to ensure starting u-u.service after logind at least tried to start and also changing u-u-s to start even with logind's absence.
[Test Case]
* Stop systemd-logind and make it unable to start for example by masking it:
root@bb-logind:~# ln -s /dev/null /etc/systemd/system/systemd-logind.service
root@bb-logind:~# systemctl daemon-reload
root@bb-logind:~# service systemd-logind stop
root@bb-logind:~# service systemd-logind status
● systemd-logind.service
Loaded: masked (/dev/null; bad)
Active: inactive (dead) since Thu 2018-12-13 13:02:44 UTC; 1s ago
Main PID: 1938 (code=killed, signal=TERM)
Status: "Processing requests..."
...
* Run u-u-s and observe it crashing in unfixed version and starting with falling back to polling logind instead taking the inhibition lock at its start:
root@bb-logind:~# /usr/share/unattended-upgrades/unattended-upgrade-shutdown --debug
root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log
...
2018-12-13 14:30:17,600 WARNING - Could not get delay inhibitor lock
2018-12-13 14:30:17,601 DEBUG - Skip waiting for signals, starting operation now
2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes
2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration
2018-12-13 14:30:17,602 DEBUG - get_lock returned 7
2018-12-13 14:30:17,602 DEBUG - lock not taken
* Restore logind's ability to start
root@bb-logind:~# rm /etc/systemd/system/systemd-logind.service
root@bb-logind:~# systemctl daemon-reload
* Restart unattended-upgrades.service
root@bb-logind:~# service unattended-upgrades restart
root@bb-logind:~# service unattended-upgrades status
● unattended-upgrades.service - Unattended Upgrades Shutdown
Loaded: loaded (/lib/systemd/system/unattended-upgrades.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2018-12-13 14:31:43 UTC; 3s ago
Docs: man:unattended-upgrade(8)
Main PID: 4129 (unattended-upgr)
Tasks: 2 (limit: 4915)
CGroup: /system.slice/unattended-upgrades.service
└─4129 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
Dec 13 14:31:43 bb-logind systemd[1]: Started Unattended Upgrades Shutdown.
root@bb-logind:~# tail /var/log/unattended-upgrades/unattended-upgrades-shutdown.log
2018-12-13 14:30:17,601 DEBUG - Starting countdown of 25.0 minutes
2018-12-13 14:30:17,602 DEBUG - Initializing apt_pkg configuration
2018-12-13 14:30:17,602 DEBUG - get_lock returned 7
2018-12-13 14:30:17,602 DEBUG - lock not taken
2018-12-13 14:31:43,595 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running
2018-12-13 14:31:43,688 WARNING - Could not get delay inhibitor lock
2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead.
2018-12-13 14:31:43,691 WARNING - Maybe systemd-logind service is not running.
2018-12-13 14:31:43,691 WARNING - Unable to monitor PrepareForShutdown() signal, polling instead.
2018-12-13 14:31:43,691 WARNING - To enable monitoring the PrepareForShutdown() signal instead of polling please install the python3-gi package
root@bb-logind:~# systemd-analyze dot | grep unattended
...
"unattended-upgrades.service"->"systemd-logind.service" [color="green"];
...
[Regression Potential]
* The change to service ordering is unlikely to cause any issue, but the graceful handling of missing logind involved a small-scale refactoring of u-u-s's code. Extensive testing did not reveal regressions in that area, but potential bugs may cause u-u.service fail to start and affect graceful shutdown of u-u the same way as detailed in [Impact].
[Original Bug Text]
The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.7, the problem page at https://errors.ubuntu.com/problem/caf5d885046359f4857cee6c4a61e1d72d0913b1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.
Also seen as:
* https://errors.ubuntu.com/problem/ac61b23e0ec25a291427b875bf213fdd5b097fa5 |
|
| 2018-12-13 14:50:37 |
Balint Reczey |
summary |
/usr/share/unattended-upgrades/unattended-upgrade-shutdown:dbus.exceptions.DBusException(org.freedesktop.DBus.Error.TimedOut):activate_name_owner:get_name_owner:call_blocking:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@373:main:__init__:get_logind_proxy:get_object:__init__:activate_name_owner:start_service_by_name:call_blocking |
[regression] Crashing with dbus.exceptions.DBusException when logind can't be started (yet) |
|
| 2018-12-13 14:54:21 |
Balint Reczey |
tags |
bionic |
bionic regression-update |
|
| 2018-12-13 15:37:15 |
Łukasz Zemczak |
unattended-upgrades (Ubuntu Cosmic): status |
New |
Fix Committed |
|
| 2018-12-13 15:37:17 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-12-13 15:37:20 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2018-12-13 15:37:22 |
Łukasz Zemczak |
tags |
bionic regression-update |
bionic regression-update verification-needed verification-needed-cosmic |
|
| 2018-12-13 15:38:24 |
Łukasz Zemczak |
unattended-upgrades (Ubuntu Bionic): status |
New |
Fix Committed |
|
| 2018-12-13 15:38:27 |
Łukasz Zemczak |
tags |
bionic regression-update verification-needed verification-needed-cosmic |
bionic regression-update verification-needed verification-needed-bionic verification-needed-cosmic |
|
| 2018-12-13 15:53:19 |
Łukasz Zemczak |
unattended-upgrades (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2018-12-13 15:53:23 |
Łukasz Zemczak |
tags |
bionic regression-update verification-needed verification-needed-bionic verification-needed-cosmic |
bionic regression-update verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
|
| 2018-12-13 19:26:59 |
Launchpad Janitor |
unattended-upgrades (Ubuntu): status |
New |
Fix Released |
|
| 2018-12-15 13:34:27 |
Francis Ginther |
tags |
bionic regression-update verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
bionic id-5c1281350678792b80fdc206 regression-update verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
|
| 2018-12-19 18:45:53 |
Balint Reczey |
tags |
bionic id-5c1281350678792b80fdc206 regression-update verification-needed verification-needed-bionic verification-needed-cosmic verification-needed-xenial |
bionic id-5c1281350678792b80fdc206 regression-update verification-done verification-done-bionic verification-done-cosmic verification-done-xenial |
|
| 2018-12-19 22:24:07 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2018-12-19 22:24:22 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-12-19 22:34:10 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Cosmic): status |
Fix Committed |
Fix Released |
|
| 2019-02-28 13:01:16 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2019-02-28 13:01:20 |
Łukasz Zemczak |
tags |
bionic id-5c1281350678792b80fdc206 regression-update verification-done verification-done-bionic verification-done-cosmic verification-done-xenial |
bionic id-5c1281350678792b80fdc206 regression-update verification-done-bionic verification-done-cosmic verification-needed verification-needed-xenial |
|
| 2019-03-12 18:03:53 |
Balint Reczey |
tags |
bionic id-5c1281350678792b80fdc206 regression-update verification-done-bionic verification-done-cosmic verification-needed verification-needed-xenial |
bionic id-5c1281350678792b80fdc206 regression-update verification-done verification-done-bionic verification-done-cosmic verification-done-xenial |
|
| 2019-04-25 10:50:00 |
Launchpad Janitor |
unattended-upgrades (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
