[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.2 --- unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium * Don't check blacklist too early and report updates from not allowed origins as kept back. (LP: #1781176) * test/test_blacklisted_wrong_origin.py: Fix and enable test * Filter out progress indicator from dpkg log (LP: #1599646) * Clear cache when autoremoval fails (LP: #1779157) * Find autoremovable kernel packages using the patterns in APT's way (LP: #1815494) unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) xenial; urgency=medium * Start service after systemd-logind.service to be able to take inhibition lock (LP: #1806487) * Handle gracefully when logind is down (LP: #1806487) unattended-upgrades (1.1ubuntu1.18.04.7~16.04.0) xenial; urgency=medium * Backport to Xenial (LP: #1702793) * Revert to build-depending on debhelper (>= 9~) and dh-systemd * Revert configuration example changes to avoid triggering a debconf question * debian/postinst: Update recovery to be triggered on Xenial's package versions unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium * Trigger unattended-upgrade-shutdown actions with PrepareForShutdown() Performing upgrades in service's ExecStop did not work when the upgrades involved restarting services because systemd blocked other stop/start actions making maintainer scripts time out and be killed leaving a broken system behind. Running unattended-upgrades.service before shutdown.target as a oneshot service made it run after unmounting filesystems and scheduling services properly on shutdown is a complex problem and adding more services to the mix make it even more fragile. The solution of monitoring PrepareForShutdown() signal from DBus allows Unattended Upgrade to run _before_ the jobs related to shutdown are queued thus package upgrades can safely restart services without risking causing deadlocks or breaking part of the shutdown actions. Also ask running unattended-upgrades to stop when shutdown starts even in InstallOnShutdown mode and refactor most of unattended-upgrade-shutdown to UnattendedUpgradesShutdown class. (LP: #1778219) * Increase logind's InhibitDelayMaxSec to 30s. (LP: #1778219) This allows more time for unattended-upgrades to shut down gracefully or even install a few packages in InstallOnShutdown mode, but is still a big step back from the 30 minutes allowed for InstallOnShutdown previously. Users enabling InstallOnShutdown node are advised to increase InhibitDelayMaxSec even further possibly to 30 minutes. - Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown changes * Ignore "W503 line break before binary operator" because it will become the best practice and breaks the build * Stop using ActionGroups, they interfere with apt.Cache.clear() causing all autoremovable packages to be handled as newly autoremovable ones and be removed by default. Dropping ActionGroup usage does not slow down the most frequent case of not having anything to upgrade and when there are packages to upgrade the gain is small compared to the actual package installation. Also collect autoremovable packages before adjusting candidates because that also changed .is_auto_removable attribute of some of them. (LP: #1803749) (Closes: #910874) unattended-upgrades (1.1ubuntu1.18.04.6) bionic; urgency=medium * Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it is available. Also stop running when reacquiring the lock fails. Thanks to Julian Andres Klode for original partial patch (LP: #1789637) * Skip rebuilding python-apt in upgrade autopkgtests. Python-apt has a new build dependency making the rebuilding as is failing and the reference handling issue is worked around in unattended-upgrades already. (LP: #1781586) * Stop trying when no adjustment could be made and adjust package candidates only to lower versions (LP: #1785093) * Skip already adjusted packages from being checked for readjusting. This makes it clearer that the recursion ends and can also be a bit quicker. (LP: #1785093) unattended-upgrades (1.1ubuntu1.18.04.5) bionic; urgency=medium * Stop updating the system when reacquiring the dpkg system lock fails. (LP: #1260041) unattended-upgrades (1.1ubuntu1.18.04.4) bionic; urgency=medium * Redirect stderr output in upgrade-between-snapshots, too, otherwise it breaks the test sometimes (LP: #1781446) unattended-upgrades (1.1ubuntu1.18.04.3) bionic; urgency=medium * Redirect stderr output in upgrade-all-security, otherwise it breaks the test (LP: #1781446) unattended-upgrades (1.1ubuntu1.18.04.2) bionic; urgency=medium [ Balint Reczey ] * Clear cache when autoremoval is invalid for a package set marked for removal and cle
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Tested 1.1ubuntu1.18.04.7~16.04.2 on Xenial: root@x-uu-lp-1690980:~# tail -f /var/log/unattended-upgrades/unattended-upgrades.log 2019-04-09 13:08:24,515 INFO Initial blacklisted packages: 2019-04-09 13:08:24,516 INFO Initial whitelisted packages: 2019-04-09 13:08:24,516 INFO Starting unattended upgrades script 2019-04-09 13:08:24,516 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial', 'o=Ubuntu,a=xenial-updates'] 2019-04-09 15:01:44,987 INFO Initial blacklisted packages: 2019-04-09 15:01:44,988 INFO Initial whitelisted packages: 2019-04-09 15:01:44,988 INFO Starting unattended upgrades script 2019-04-09 15:01:44,988 INFO Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates 2019-04-09 15:02:06,773 INFO Packages that will be upgraded: adwaita-icon-theme dirmngr fontconfig fontconfig-config gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 glib-networking glib-networking-common glib-networking-services gnupg-agent gnupg2 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-x hicolor-icon-theme humanity-icon-theme hwdata libarchive13 libavahi-client3 libavahi-common-data libavahi-common3 libboost-filesystem1.58.0 libboost-iostreams1.58.0 libboost-system1.58.0 libcaca0 libcups2 libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libegl1-mesa libepoxy0 libexempi3 libfontconfig1 libgbm1 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgraphite2-3 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libharfbuzz0b libinput10 libjpeg-turbo8 libksba8 liblcms2-2 libllvm3.8 libmirclient9 libmirprotobuf3 libnautilus-extension1a libnspr4 libnss3 libnss3-nssdb libpam-systemd libpulse0 libsane libsane-common libsndfile1 libsoup-gnome2.4-1 libsoup2.4-1 libsystemd0 libtiff5 libtracker-sparql-1.0-0 libudev1 libvorbis0a libvorbisenc2 libwacom-bin libwacom-common libwacom2 libwavpack1 libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libx11-xcb1 libxcursor1 libxkbcommon0 libxpm4 systemd systemd-sysv ubuntu-mono udev wget x11-common 2019-04-09 15:02:06,774 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log ^C root@x-uu-lp-1690980:~# dbus-send --system --print-reply --dest=org.freedesktop.login1 /org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false method return time=1554822131.758122 sender=:1.1 -> destination=:1.7 serial=33 reply_serial=2 root@x-uu-lp-1690980:~# root@x-uu-lp-1690980:~# tail -f /var/log/unattended-upgrades/unattended-upgrades.log 2019-04-09 13:08:24,516 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial', 'o=Ubuntu,a=xenial-updates'] 2019-04-09 15:01:44,987 INFO Initial blacklisted packages: 2019-04-09 15:01:44,988 INFO Initial whitelisted packages: 2019-04-09 15:01:44,988 INFO Starting unattended upgrades script 2019-04-09 15:01:44,988 INFO Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates 2019-04-09 15:02:06,773 INFO Packages that will be upgraded: adwaita-icon-theme dirmngr fontconfig fontconfig-config gir1.2-gdkpixbuf-2.0 gir1.2-gtk-3.0 glib-networking glib-networking-common glib-networking-services gnupg-agent gnupg2 gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-x hicolor-icon-theme humanity-icon-theme hwdata libarchive13 libavahi-client3 libavahi-common-data libavahi-common3 libboost-filesystem1.58.0 libboost-iostreams1.58.0 libboost-system1.58.0 libcaca0 libcups2 libdrm-amdgpu1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libegl1-mesa libepoxy0 libexempi3 libfontconfig1 libgbm1 libgd3 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-common libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libgraphite2-3 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libgtk-3-0 libgtk-3-bin libgtk-3-common libharfbuzz0b libinput10 libjpeg-turbo8 libksba8 liblcms2-2 libllvm3.8 libmirclient9 libmirprotobuf3 libnautilus-extension1a libnspr4 libnss3 libnss3-nssdb libpam-systemd libpulse0 libsane libsane-common libsndfile1 libsoup-gnome2.4-1 libsoup2.4-1 libsystemd0 libtiff5 libtracker-sparql-1.0-0 libudev1 libvorbis0a libvorbisenc2 libwacom-bin libwacom-common libwacom2 libwavpack1 libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa libwayland-server0 libx11-xcb1 libxcursor1 libxkbcommon0 libxpm4 systemd systemd-sysv ubuntu-mono udev wget x11-common 2019-04-09 15:02:06,774 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2019-04-09 15:02:11,761 WARNING SIGTERM received, will stop 2019-04-09 15:02:14,904 WARNING SIGTERM received, will stop 2019-04-09 15:02:17,763 WARNING SIGTERM received, will stop 2019-04-09 15:02:20,
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Hello ethan.hsieh, or anyone else affected, Accepted unattended-upgrades into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.7~16.04.0 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Description changed:
Title: No pop-up window to warn users that system should not reboot or
shutdown while installing security updates
Summary:
No pop-up window to warn users that system should not reboot or shutdown
while installing security updates
Steps:
1. trigger unattended-upgrades
2. reboot or shutdown system while installing packages
Expected results: There is a pop-up window to warn users that system
should not reboot or shutdown
Actual results: There is no pop-up window to warn users
Additional information:
$ apt-cache policy unattended-upgrades
unattended-upgrades:
Installed: 0.90
Candidate: 0.90ubuntu0.5
$ lsb_release -rd
Description:Ubuntu 16.04 LTS
-
* APT SRU *
[Impact]
Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the
signals to all processes in the cgroup, and will send KILL quickly after.
[Test case]
Start apt-daily-upgrade.service and stop it while unattended-upgrades is
running.
The upgrade should run to completion or a safe exit point as long as it
takes less than about 900s (which is the timeout for sending kill).
[Regression potential]
Leftover processes might remain in the apt-daily-upgrade cgroup if the
postinst scripts or some apt hooks do something funny.
Shutdown might take longer due to the 900 second timeout.
+
+ * unattended-upgrades SRU
+
+ [Impact]
+
+ * Undattended-upgrades does not stop quickly gracefully when shutdown/reboot
is initiated by the user.
+ * The fix is performing the updates in minimal package sets and allow
gracefully stopping between those steps when unattended-upgrades.service sends
a TERM signal to running u-u. The signal is sent on receiving
PrepareForShutdown() from logind
(https://www.freedesktop.org/wiki/Software/systemd/inhibit/) to stop
unattended-upgrades a bit earlier than the shutdown process starts (LP:
#1803137).
+
+ [Test Case]
+
+ * Configure the system to have several 20+ packages upgradable by
+ unattended-upgrades. One easy way of setting this up is starting with a
+ system where packages from -security are installed but packages from
+ -updates are not and enabling -updates in u-u:
+
+ # echo 'Unattended-Upgrade::Allowed-Origins::
+ "${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
+ /51unattended-upgrades-updates-too
+
+ * Pre-download upgrades
+ # unattended-upgraded --download-only
+
+ * Trigger unattended-upgrades run:
+ # service apt-daily-upgrade start
+
+ * Shutdown the system from a graphical user session or by executing
+ # dbus-send --system --print-reply --dest=org.freedesktop.login1
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false
+
+ * Observe the system unattended-upgrades being gracefully stopped,
+ checking /var/log/unattended-upgrades/unattended-upgrades.log. There
+ should be packages left to be upgraded.
+
+ [Regression Potential]
+
+ On Xenial (with Unity) starting shutdown from the graphical session does
+ not log the user out nor show any progress on the shutdown until the
+ inhibition timer expires which is confusing. Users should be logged out
+ on PrepareForShutdown() (LP: #1803581).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690980
Title:
unattended-upgrades does not block shutdown of system, as it is
designed to
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: oem-priority/xenial Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Tags added: id-5a37e0a701a3f39adbe6e4b9 ** Tags added: id-5a816b8dd2d5924dccc5ba62 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
This bug was fixed in the package apt - 1.2.25 --- apt (1.2.25) xenial; urgency=medium * Microrelease covering 1.4.7 (LP: #1702326) and 1.4.8 [ Robert Luberda ] * fix a "critical" typo in old changelog entry (Closes: 866358) [ David Kalnischkies ] * use port from SRV record instead of initial port * don't ask an uninit _system for supported archs (LP: #1613184) [ Julian Andres Klode ] * Reset failure reason when connection was successful * http: A response with Content-Length: 0 has no content * apt-daily: Pull in network-online.target in service, not timer (LP: #1716973) [ Balint Reczey ] * Gracefully terminate process when stopping apt-daily-upgrade (LP: #1690980) -- Julian Andres Klode Tue, 26 Sep 2017 16:14:54 +0200 ** Changed in: apt (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The apt side should be OK. But it depends on interaction with other services, so it cannot be reliably tested on its own I guess. We'll get a better fix eventually that makes the apt side work better by making it wait on the upgrade itself. Currently, we basically stop the controlling script; and then u-u continues running and the shutdown is blocked by u-u.service waiting for it ** Tags removed: verification-needed-xenial verification-needed-zesty ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I don't see anything here left to sponsor so I'm unsubscribing the sponsors team. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Ubuntu 17.04 has reached end of life. No further bugfixes will be applied to this version. ** Changed in: apt (Ubuntu Zesty) Status: Fix Committed => Won't Fix ** Changed in: unattended-upgrades (Ubuntu Zesty) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: oem-priority/xenial Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I booted my xenial system in a VM, and tried to verify it; but: The hierarchy of apt-daily-upgrade.service is: apt.system.daily install - apt.systemd.daily lock_is_held install - unattended-upgrades only the top-level process is terminated. Manually sending SIGTERM to unattended-upgrades makes it exit; but it seems the SIGTERM is not forwarded through the shells. The result is simple: The big lock protecting against update and co is released (not that problematic), but upgrades are never stopped. I'm not sure if systemd still waits for the runaway processes on shutdown; if that's the case, then it sort of works. We'd have to verify that somehow. So, if we want to have a time out working, we have to get rid of the shell script it seems. Which sucks a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
A work around would be to invoke subprocesses using:
_term() {
kill -TERM "$child" 2>/dev/null
}
trap _term SIGTERM
run() {
"$@" &
child="$!"
wait "$child"
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690980
Title:
unattended-upgrades does not block shutdown of system, as it is
designed to
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
It would be great if someone else could verify the SRUs for xenial and zesty? I don't have full VMs lying around to start / stop the service. (I have a dual boot (x)ubuntu on my HDD, but that's slow, and only one) We really should get these updates out of the door soon, /me thinks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: oem-priority/xenial Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Tags added: id-596781a4fd7307546010c061 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Hello ethan.hsieh, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.25 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Description changed: Title: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Summary: No pop-up window to warn users that system should not reboot or shutdown while installing security updates Steps: 1. trigger unattended-upgrades 2. reboot or shutdown system while installing packages Expected results: There is a pop-up window to warn users that system should not reboot or shutdown Actual results: There is no pop-up window to warn users Additional information: $ apt-cache policy unattended-upgrades unattended-upgrades: - Installed: 0.90 - Candidate: 0.90ubuntu0.5 + Installed: 0.90 + Candidate: 0.90ubuntu0.5 $ lsb_release -rd Description:Ubuntu 16.04 LTS + + + * APT SRU * + [Impact] + Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the signals to all processes in the cgroup, and will send KILL quickly after. + + [Test case] + Start apt-daily-upgrade.service and stop it while unattended-upgrades is running. + + The upgrade should run to completion or a safe exit point as long as it + takes less than about 900s (which is the timeout for sending kill). + + [Regression potential] + Leftover processes might remain in the apt-daily-upgrade cgroup if the postinst scripts or some apt hooks do something funny. + + Shutdown might take longer due to the 900 second timeout. ** Changed in: apt (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Hello ethan.hsieh, or anyone else affected, Accepted apt into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.4.8 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: apt (Ubuntu Zesty) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan On Fri, Sep 22, 2017 at 12:21 PM, ethan.hsieh wrote: > @Balint > > Here is test result for InstallOnShutdown:false > > Timestamp: > 1. 13:25:10~13:40:32: 15mins > 2. reboot system > 3. 14:59:17~16:44:18: 1hr45mins > Total: 2hr > > Comparing to the test result in #69, 0.97ubuntu1~16.04.1 saves 4~5 > hours. > > Log: Please check full log as attached. Thanks! looking at the logs there is still some room for improvements and I have some in my mind but they are more risky and should be applied after Artful's release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan On Fri, Sep 22, 2017 at 9:29 AM, ethan.hsieh wrote: > @Balint > > Here is test result for InstallOnShutdown:true > > "Errors were encountered while processing: apport" > u-u still has packages to upgrade after this issue happens. > So, when I reboot system every time, u-u still tries to upgrade package. > We expect that there are 30 mins to do the update. > But, dependency problem will prevent u-u from upgrading packages. > > 1. unattended-upgrades-shutdown.log: (Please check full log as attached) > > 2017-09-22 14:54:25,865 WARNING - Running unattended-upgrades in shutdown mode > 14:54:25~14:55:54 => 1:29, u-u only takes 1:29 to upgrade packges. > 2017-09-22 14:57:02,183 WARNING - Running unattended-upgrades in shutdown mode > 14:57:02~14:58:30 => 1:28 > 2017-09-22 15:00:00,233 WARNING - Running unattended-upgrades in shutdown mode > 15:00:00~15:01:28 => 1:28 > > > 2. unattended-upgrades-dpkg.log: > > Log started: 2017-09-22 14:34:24 > ... > Preparing to unpack .../apport_2.20.1-0ubuntu2.10_all.deb ... > Failed to get load state of apport-forward.socket: Connection reset by peer > 2017-09-22 14:37:26,769 WARNING SIGTERM received, will stop > Log ended: 2017-09-22 14:37:26 > Thanks for the tests and the logs! It looks like this is an apport issue and u-u can't do much about it. I think upgrading services _during shutdown_ is something they are generally not prepared for and to support InstallOnShutdown:true system-wide packages need to be tested and be prepared with that scenario in mind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is test result for InstallOnShutdown:false Timestamp: 1. 13:25:10~13:40:32: 15mins 2. reboot system 3. 14:59:17~16:44:18: 1hr45mins Total: 2hr Comparing to the test result in #69, 0.97ubuntu1~16.04.1 saves 4~5 hours. Log: Please check full log as attached. Installed packages: apt (1.2.25-rbalint2) unattended-upgrades_0.97ubuntu1~16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4954978/+files/log_0922_InstallOnShutdown_False.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
typo... u-u in #73 should be 0.97ubuntu1~16.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is test result for InstallOnShutdown:true "Errors were encountered while processing: apport" u-u still has packages to upgrade after this issue happens. So, when I reboot system every time, u-u still tries to upgrade package. We expect that there are 30 mins to do the update. But, dependency problem will prevent u-u from upgrading packages. 1. unattended-upgrades-shutdown.log: (Please check full log as attached) 2017-09-22 14:54:25,865 WARNING - Running unattended-upgrades in shutdown mode 14:54:25~14:55:54 => 1:29, u-u only takes 1:29 to upgrade packges. 2017-09-22 14:57:02,183 WARNING - Running unattended-upgrades in shutdown mode 14:57:02~14:58:30 => 1:28 2017-09-22 15:00:00,233 WARNING - Running unattended-upgrades in shutdown mode 15:00:00~15:01:28 => 1:28 2. unattended-upgrades-dpkg.log: Log started: 2017-09-22 14:34:24 ... Preparing to unpack .../apport_2.20.1-0ubuntu2.10_all.deb ... Failed to get load state of apport-forward.socket: Connection reset by peer 2017-09-22 14:37:26,769 WARNING SIGTERM received, will stop Log ended: 2017-09-22 14:37:26 Installed packages: apt (1.2.25-rbalint2) unattended-upgrades_0.96ubuntu1-16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4954864/+files/log_0922_InstallOnShutdown.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan Based on profiling real-life scenario (updating unstable with 100+ packages) I believe I was able to make u-u ~10 > times faster that should bring down the time of your test of upgrading xenial with all security updates to below one hour. Since running only dpkg's part took more than 30 minutes I think this state is good for Artful and for backporting the fixes to older releases. I've set up a separate PPA for u-u testing if you would like to verify the speedup & other fixes: https://launchpad.net/~rbalint/+archive/ubuntu/unattended-upgrades -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
It is also worth noting that users should rarely meet such slow upgrade as the number of packages to upgrade with each run is usually much lower. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan: Thanks for the test and the logs. Those show that the fix works but the move to minimal steps slowed down u-u a lot. I tried fixing the slowdown by finishing the concept of pre-calculating the steps then performing them but IMO this direction is not safe and can potentially leave packages not-upgraded due to inter-dependencies between pre-calculated upgrade steps: https://github.com/mvo5/unattended-upgrades/tree/feature/minimal-upgrades-speedup2 I'm now profiling u-u instead to find where the slowdown is coming from and try fixing that instead of pre-calculating the steps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is another test result for InstallOnShutdown:false Log: 2017-09-14 17:20:14 ~ 2017-09-15 00:00:03 It took 6~7 hours to finish online update. (Packages: around 700mb) unattended-upgrades.log // Online update was triggered. 2017-09-14 17:15:03,561 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] // Reboot system manually 2017-09-14 18:07:49,988 WARNING SIGTERM received, will stop // Online udpate didn't be finished. apt-daily-upgrade triggerred it again. 2017-09-14 18:16:29,208 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] (Please check full log as attached) $ grep -r -e "Install" 50unattended-upgrades // Install all unattended-upgrades when the machine is shutting down //Unattended-Upgrade::InstallOnShutdown "true"; Installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.96ubuntu1-16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4950491/+files/log_0914_InstallOnShutdown_False.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan, On Thu, Sep 14, 2017 at 12:04 PM, ethan.hsieh wrote: > @Balint > > Here is my test result: (InstallOnShutdown:true) > > Packages will be installed when rebooting system. > I rebooted system five times, but system still didn't finish the update. > It took too long to finish online update. > > Timestamp: (reboot system) > 1. 2017-09-14 13:57:00,998 > 2. 2017-09-14 14:32:26,172 > 3. 2017-09-14 15:20:41,267 > 4. 2017-09-14 16:00:18,694 > 5. 2017-09-14 16:36:47,174 > (Please check full log as attached) Thanks for the tests, there are several interesting things in it. The first one is that upgrades took very long time and I opened an upstream issue for that: https://github.com/mvo5/unattended-upgrades/issues/76 The second is that u-u properly blocks shutdown so this bug seems to be fixed for the tested case. The third is the presence of the crash file in 3/ which is a result of killing u-u --download and it is normal, thus u-u should not generate it. I'll fix that separately. ** Bug watch added: github.com/mvo5/unattended-upgrades/issues #76 https://github.com/mvo5/unattended-upgrades/issues/76 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Here is my test result: (InstallOnShutdown:true) Packages will be installed when rebooting system. I rebooted system five times, but system still didn't finish the update. It took too long to finish online update. Timestamp: (reboot system) 1. 2017-09-14 13:57:00,998 2. 2017-09-14 14:32:26,172 3. 2017-09-14 15:20:41,267 4. 2017-09-14 16:00:18,694 5. 2017-09-14 16:36:47,174 (Please check full log as attached) $ apt-config dump Unattended-Upgrade::InstallOnShutdown "true"; Installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.96ubuntu1-16.04.1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4950042/+files/log_0914_InstallOnShutdown_True.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: unattended-upgrades (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Incomplete ** Changed in: apt (Ubuntu Xenial) Status: Incomplete => Triaged ** Changed in: apt (Ubuntu Zesty) Status: New => Triaged ** Changed in: apt (Ubuntu) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Zesty) Importance: Undecided => Critical ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan: Re: ping over IRC, yes, please apt_1.2.25-rbalint2 for testing u-u. When Unattended-Upgrade::InstallOnShutdown is set u-u should also work properly with apt 1.2.24 from -updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan: I have uploaded unattended-upgrades_0.96ubuntu1~16.04.1 for testing to https://launchpad.net/~rbalint/+archive/ubuntu/scratch , too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
This bug was fixed in the package unattended-upgrades - 0.96ubuntu1 --- unattended-upgrades (0.96ubuntu1) artful; urgency=low * Merge from Debian unstable (LP: #1714019) - Remaining changes: - Recover from broken dh_installinit override in versions < 0.93.1ubuntu3 - unattended-upgrades: Do not automatically upgrade the development release of Ubuntu unless Unattended-Upgrade::DevRelease is true. - Dropped changes, included in Debian: - Cherry-pick 2e5deed, f26edb4 from upstream to add support for a --download-only option, enabling us to download updates at a random time of day by default but apply them predictably in the 6am-7am window. - Fix PEP8 failures (replace except: with except Exception:) - unattended-upgrades: Provide some information and create a log entry when there is a failure to parse the allowed origins. - Add UbuntuESM to the list of sources automatically upgraded from by default. - Complete the solution for the unattended-upgrades.service unit not correctly working - d/rules : Remove the override_dh_installinit. The stop option is no longer available so the command falls back to default. This is the normal behavior so the override is not required - d/unattended-upgrades.init : Add Default-Start runlevels, otherwise the unattended-upgrades.service unit cannot be enabled on boot - d/postinst : Cleanup the stop symlinks created by the wrong override_dh_installinit. Without that, the systemd unit cannot be enabled correctly. Force disable the service before deb-systemd-helper runs so the old symlink is not left dangling (workaround for Debian Bug #797108). Force enable and start of the systemd unit to work around Debian Bug #797108 which fails to enable systemd units correctly when WantedBy= statement is changed which is the case here. - d/unattended-upgrades.service : Fix the service so it runs correctly on shutdown : - Remove DefaultDependencies=no : Breaks normal shutdown dependencies - Set After= to network.target and local-fs.target. Since our service is now ExecStop, it will run before network and local-fs become unavailable. - Add RequiresMountsFor=/var/log /var/run /var/lib /boot : Necessary if /var is a separate file system. Set WantedBy= to multi-user.target - Add DEP8 tests to verify the following : - Verify that the unattended-upgrades.service unit is enabled and started. - Verify that InstallOnShutdown works when configured. - The systemd unit needs to be an ExecStop since it is is activated on shutdown. Otherwise, it will get scheduled after completion of the local-fs.target. In the case where /var is a separate filesystem, unattended-upgrade-shutdown will hang until timeout since /var/run is expected but no longer there - When performing a sanity check for packages to install or upgrade return false when either there are no packages in the cache or the package to upgrade is not in the change set. - Do not mark packages for deletion / autoremoval if unattended-upgrades is being run in dry-run mode. - Store delay command line option as an int not a string since we do maths with it. -- Balint Reczey Wed, 30 Aug 2017 13:46:37 +0200 ** Changed in: unattended-upgrades (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Correct changelog: apt (1.5~beta2) unstable; urgency=medium [ M. Willis Monroe ] * Minor grammar fix [ Zhou Mo ] * zh_CN.po: update Simplified Chinese programs translation [ David Kalnischkies ] * don't expect more downloads from failed transactions * remove reference to a-t-debtorrent in description * ignore SIGPIPE in dump solver if forwarding * support compressed extended_states file for bug triage * don't move failed pdiff indexes out of partial (Closes: 869425) * don't try to parse all fields starting with HTTP as status-line * send weak-only hashes to methods * fail earlier if server answers with too much data * fail early in http if server answer is too small as well * use FileFd to parse all apt configuration files * show warnings instead of errors if files are unreadable (LP: #1701852) * reimplement and document auth.conf (Closes: #811181) * lookup login info for proxies in auth.conf * allow the auth.conf to be root:root owned * update URI scheme descriptions in sources.list(5) * show a warning for Debian shutting down FTP services * suggest using auth.conf for sources with passwords * ftparchive: sort discovered filenames before writing indexes. Thanks to Chris Lamb for initial patch & Stefan Lippers-Hollmann for testing (Closes: 869557) * don't keep configuration files open needlessly * don't hang if multiple sources use unavailable method (Closes: 870675) [ Beatrice Torracca ] * Italian manpage translation update (Closes: 858877) [ Apollon Oikonomopoulos ] * Handle supported components with slashes in sources.list (Closes: #868127) [ Julian Andres Klode ] * Drop cacheiterators.h include * methods/aptmethod.h: Add missing fileutl.h include * Reformat and sort all includes with clang-format * cacheiterators: Warn about direct include and don't include pkgcache.h * Update gitignore with new files * Use C++11 threading support instead of pthread * Always warn if --force-yes is validly specified, not just if used * Work around float rounding change in gcc 7 on i386 * Handle GCC 7 std::string operator ABI break (Closes: #871275) * debian: Update symbols for libapt-pkg5.0 [ Paul Wise ] * Support zero delay for the various APT::Periodic activities * Support seconds, minutes, hours and days for APT::Periodic intervals * Switch from /org to /srv in example apt-ftparchive configuration [ Balint Reczey ] * Gracefully terminate process when stopping apt-daily-upgrade (LP: #1690980) [ Dominik ] * doc: Add '--allow-unauthenticated' to '--force-yes' -- Julian Andres Klode Thu, 17 Aug 2017 19:28:00 +0200 (sorry, I did not generate the .changes file against 1.5~beta1...). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
This bug was fixed in the package apt - 1.5~rc1~ubuntu1 --- apt (1.5~rc1~ubuntu1) artful; urgency=medium * Redefine APT_CONST to mean APT_PURE * Replace APT_CONST with APT_PURE everywhere * Make test-bug-818628-unreadable-source work on !amd64 -- Julian Andres Klode Thu, 24 Aug 2017 17:56:28 +0200 ** Changed in: apt (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
On Tue, Aug 08, 2017 at 08:53:48AM -, ethan.hsieh wrote: > @Balint > > I tried three times, and 0.95-16.04.0rbalint1 didn't work well. > > Please refer to attached file for detailed log. > > 1) Reboot system when unattended upgrades starts to download packages. > //unattended-upgrades.log > 2017-08-08 15:34:07,782 INFO Starting unattended upgrades script > 2017-08-08 15:34:07,782 INFO Allowed origins are: ['o=Ubuntu,a=xenial', > 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] > //unattended-upgrades-shutdown.log > 2017-08-08 15:36:06,358 INFO - All upgrades installed > > The log shows "All upgrades installed", but there is no package > installed. > > 2) Reboot system after unattended upgrades downloads packages for 5mins > //unattended-upgrades.log > 2017-08-08 15:55:27,907 INFO Starting unattended upgrades script > 2017-08-08 15:55:27,907 INFO Allowed origins are: ['o=Ubuntu,a=xenial', > 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] > > System reboots immediately. There is no unattended-upgrades-shutdown > log. > > 3) Reboot system when unattended upgrades starts to download packages. > //unattended-upgrades.log > 2017-08-08 16:09:03,548 INFO Starting unattended upgrades script > 2017-08-08 16:09:03,549 INFO Allowed origins are: ['o=Ubuntu,a=xenial', > 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] > //unattended-upgrades-shutdown.log > 2017-08-08 16:10:50,573 INFO - All upgrades installed > > The log shows "All upgrades installed", but there is no package > installed. Keep in mind there is also the log file /var/log/unattended-upgrades/unattended-upgrades-dpkg.log which contains detailed information about the packages being installed. -- Brian Murray -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Ethan Yes, the "All upgrades installed" message is still misleading. Note however that there are two modes of u-u you can operate in on shutdown and they are picked by setting Unattended- Upgrade::InstallOnShutdown. When it is set to True u-u runs to completion (unless it times out after 15 minutes). In the other case (set to false) shutdown gracefully terminates u-u with the current fixes possibly (and probably) not installing every update. In that case the message is clearly misleading. I'm updating the message, but I believe that this is how u-u is expected to operate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint I tried three times, and 0.95-16.04.0rbalint1 didn't work well. Please refer to attached file for detailed log. 1) Reboot system when unattended upgrades starts to download packages. //unattended-upgrades.log 2017-08-08 15:34:07,782 INFO Starting unattended upgrades script 2017-08-08 15:34:07,782 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] //unattended-upgrades-shutdown.log 2017-08-08 15:36:06,358 INFO - All upgrades installed The log shows "All upgrades installed", but there is no package installed. 2) Reboot system after unattended upgrades downloads packages for 5mins //unattended-upgrades.log 2017-08-08 15:55:27,907 INFO Starting unattended upgrades script 2017-08-08 15:55:27,907 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] System reboots immediately. There is no unattended-upgrades-shutdown log. 3) Reboot system when unattended upgrades starts to download packages. //unattended-upgrades.log 2017-08-08 16:09:03,548 INFO Starting unattended upgrades script 2017-08-08 16:09:03,549 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] //unattended-upgrades-shutdown.log 2017-08-08 16:10:50,573 INFO - All upgrades installed The log shows "All upgrades installed", but there is no package installed. --- The installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.95-16.04.0rbalint1_all.deb ** Attachment added: "unattended-upgrades-shutdown.log, unattended-upgrades.log, apt log, and dpkg log" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4928762/+files/log_0808.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I've filed the PR to default to minimal steps fixing a few related issues: https://github.com/mvo5/unattended-upgrades/pull/70 @Brian: This should really work in your tests leaving a consistent system behind on shutdown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
For being on the safe side on slow machines I would bump the timeout even higher. I'll also file a PR setting --minimal-upgrade-steps the default which will allow upgrading in transactions by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Brian: It looks like blocking shutdown did work properly but the upgrade itself took longer than 15 minutes which is the current timeout. (see u-u.log) I already filed a PR against u-u to bump the timeout to 30 mins: https://github.com/mvo5/unattended-upgrades/pull/69 , but in this case apt's timer kicks in (@Julian). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The dpkg log file too. ** Attachment added: "unattended-upgrades-dpkg.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4924779/+files/unattended-upgrades-dpkg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I test this again in the following manner, installed apt and unattended- upgrades from Balint's PPA, then modified /etc/apt/apt.conf.d/20auto- upgrades so that APT:Periodic::Unattended-Upgrade was "1". I then ran "sudo service apt-daily-upgrade start" and ran the u-u-reboot.sh script I've mentioned before. After the reboot I ran 'sudo apt-get update' and 'sudo apt-get upgrade' which returned: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. This is the problem we are trying to avoid. I'll attach /var/log /unattended-upgrades/unattended-upgrades.log and u-u-dpkg.log. ** Attachment added: "unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4924778/+files/unattended-upgrades.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The problem causing apport's slow installation mentioned in https://bugs.launchpad.net/ubuntu/+source/unattended- upgrades/+bug/1690980/comments/37 seems to be LP: #1320403. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Re inhibitor: One can run u-u --download-only from cron first without the inhibitor then the full u-u with the inhibitor. While this method does not allow per-transaction granularity, it is a fairly good solution without added complexity. I someone comes up with a proper patch it may be integrated but I think this is out of the scope of this bug. The committed solution already provides the per-transaction stopping granularity when u-u is started by apt's service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Julian: When running u-u at shutdown the expectation is that it runs to completion including the downloads (started by u-u-s). When running in periodic mode triggered by apt's timer it finishes the transaction on TERM signal then it exits to let the shutdown continue. In this case you are right it does not perform the download and installation steps in the same service. In apt-daily-upgrade's case the 900 second is probably future-proof unless the machine/disk is very slow. There are still installer packages which need downloads even during installation, but they are not updated very often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Downloads happen in a different service, so WiFi or not should not matter. The TERM signal is sent immediately anyway; after that, unattended-upgrades stops the upgrade. unattended-upgrade splits updates into small dpkg runs and that is what we are worrying about - not the time for a complete upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Re inhibitor: unattended-upgrades should not inhibit shutdown generally. It should however do the inhibit thing per "transaction", if you know what I mean. This requires communicating with systemd via dbus I suppose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Julian, @Michael: I think the timeout of 900 seconds should be increased to 1800 seconds and the 10 min delay in u-u-s should also be bumped to 25min. Ethan experienced updates taking ~10 minutes over wifi. I believe updates will keep accumulating and are getting bigger, thus letting u-u run for 30 minutes before killing it seems to be a reasonable change to make u-u more future-proof. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
We discussed the test with Brian, and ending in inconsistent states can still occur when running u-u manually/via cron. In those cases the apt fix does not protect dpkg from being terminated early. When running u-u manually or via cron it is recommended to use workaround 3. from #19, i.e. running u-u like that: systemd-inhibit --what=shutdown,handle-hibernate-key --mode=block /usr/lib/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Here's unattended-upgrades.log when the reboot did not cause an inconsistent state: 2017-07-26 08:33:37,462 INFO Initial blacklisted packages: 2017-07-26 08:33:37,463 INFO Initial whitelisted packages: 2017-07-26 08:33:37,463 INFO Starting unattended upgrades script 2017-07-26 08:33:37,463 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] 2017-07-26 08:38:14,276 INFO Packages that will be upgraded: apparmor apport apport-gtk apt-transport-https bash bind9-host cpp-5 curl dbus dbus-x11 distro-info-data dnsutils eject evince evince-common firefox firefox-locale-en fonts-opensymbol g++-5 gcc-5 gcc-5-base ghostscript ghostscript-x gir1.2-gst-plugins-base-1.0 gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 gstreamer1.0-alsa gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-x imagemagick imagemagick-6.q16 imagemagick-common libapparmor-perl libapparmor1 libapt-inst2.0 libarchive13 libasan2 libasn1-8-heimdal libatomic1 libbind9-140 libc-bin libc-dev-bin libc6 libc6-dbg libc6-dev libcc1-0 libcilkrts5 libcurl3 libcurl3-gnutls libdbus-1-3 libdns-export162 libdns162 libevdocument3-4 libevent-2.0-5 libevview3-3 libexpat1 libfreetype6 libgc1c2 libgcc-5-dev libgcrypt20 libgd3 libgnutls-openssl27 libgnutls30 libgomp1 libgs9 libgs9-common libgssapi3-heimdal libgstr eamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhogweed4 libhx509-5-heimdal libicu55 libisc-export160 libisc160 libisccc140 libisccfg140 libitm1 libjasper1 libjavascriptcoregtk-4.0-18 libjbig2dec0 libkrb5-26-heimdal libldap-2.4-2 liblightdm-gobject-1-0 liblsan0 liblwres141 libmagickcore-6.q16-2 libmagickcore-6.q16-2-extra libmagickwand-6.q16-2 libminiupnpc10 libmpx0 libmwaw-0.3-3 libnettle6 libnl-3-200 libnl-genl-3-200 libnm-glib-vpn1 libnm-glib4 libnm-gtk-common libnm-gtk0 libnm-util2 libnm0 libnma-common libnma0 libnspr4 libnss3 libnss3-nssdb liboxideqt-qmlplugin liboxideqtcore0 liboxideqtquick0 libpcsclite1 libpoppler-glib8 libpoppler58 libpython2.7 libpython2.7-minimal libpython2.7-stdlib libpython3.5 libpython3.5-minimal libpython3.5-stdlib libquadmath0 libreoffice-avmedia-backend-gstreamer libreoffice-base-core libreoffice-calc libreoffice-common libreoffice-core libreoffice-draw libreoffice-gnome libreoff ice-gtk libreoffice-impress libreoffice-math libreoffice-ogltrans libreoffice-pdfimport libreoffice-style-breeze libreoffice-style-galaxy libreoffice-writer libroken18-heimdal librtmp1 libsmbclient libsndfile1 libssl1.0.0 libstdc++-5-dev libstdc++6 libtasn1-6 libtiff5 libtracker-sparql-1.0-0 libtsan0 libubsan0 libvncclient1 libwbclient0 libwebkit2gtk-4.0-37 libwebkit2gtk-4.0-37-gtk2 libwind0-heimdal libxml2 libxpm4 libxslt1.1 lightdm lintian linux-firmware linux-generic linux-headers-generic linux-image-generic linux-libc-dev locales login multiarch-support network-manager network-manager-gnome ntfs-3g openssl oxideqt-codecs passwd poppler-utils python2.7 python2.7-minimal python3-apport python3-cryptography python3-pil python3-problem-report python3-uno python3.5 python3.5-minimal samba-libs sudo tar tcpdump thunderbird thunderbird-gnome-support thunderbird-locale-en thunderbird-locale-en-us tzdata uno-libs3 ure vim vim-common vim-runtime vim-tiny xserver-common xserver-xorg-core 2017-07-26 08:38:14,276 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2017-07-26 08:38:15,406 WARNING SIGTERM received, will stop Here is the unattended-upgrades.log which produced the inconsistent state: 2017-07-26 09:19:02,321 INFO Initial blacklisted packages: 2017-07-26 09:19:02,322 INFO Initial whitelisted packages: 2017-07-26 09:19:02,322 INFO Starting unattended upgrades script 2017-07-26 09:19:02,322 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] 2017-07-26 09:19:02,323 WARNING Unclean dpkg state detected, trying to correct 2017-07-26 09:19:03,101 WARNING dpkg --configure -a output: Setting up man-db (2.7.5-1) ... Setting up login (1:4.2-3.1ubuntu5.3) ... 2017-07-26 09:23:24,398 INFO Packages that will be upgraded: apparmor apport apport-gtk apt-transport-https bind9-host cpp-5 curl dbus dbus-x11 distro-info-data dnsutils eject evince evince-common firefox firefox-locale-en fonts-opensymbol g++-5 gcc-5 gcc-5-base ghostscript ghostscript-x gir1.2-gst-plugins-base-1.0 gir1.2-javascriptcoregtk-4.0 gir1.2-webkit2-4.0 gstreamer1.0-alsa gstreamer1.0-plugins-base gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good gstreamer1.0-pulseaudio gstreamer1.0-x imagemagick imagemagick-6.q16 imagemagick-common libapparmor-perl libapparmor1 libapt-inst2.0 libarchive13 libasan2 libasn1-8-heimdal libatomic1 libbind9-140 libc-bin libc-dev-bin libc6 libc6-dbg libc6-dev libcc1-0 libcilkrts5 libcurl3 libcurl3-gnutls libdbus-1-3 libdns-export162 lib
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Brian: Thanks! Verbose/debug mode seems to cause the errors and possibly the inconsistent state, too, due to u-u crashing early. The other case where you can still get an inconsistent state is when u-u takes more than 15 minutes to install all the packages in a way that it can't be interrupted in the last 5 minutes. Do you have something in the logs to verify one of the theories? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
bdmurray@clean-xenial-amd64:~$ apt-cache policy unattended-upgrades unattended-upgrades: Installed: 0.93.2~16.04.0+rbalint3 Candidate: 0.93.2~16.04.0+rbalint3 Version table: *** 0.93.2~16.04.0+rbalint3 500 500 http://ppa.launchpad.net/rbalint/scratch/ubuntu xenial/main amd64 Packages 500 http://ppa.launchpad.net/rbalint/scratch/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status 0.90ubuntu0.6 500 500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages 500 http://192.168.10.7/ubuntu xenial-updates/main i386 Packages 0.90ubuntu0.1 500 500 http://192.168.10.7/ubuntu xenial-security/main amd64 Packages 500 http://192.168.10.7/ubuntu xenial-security/main i386 Packages 0.90 500 500 http://192.168.10.7/ubuntu xenial/main amd64 Packages 500 http://192.168.10.7/ubuntu xenial/main i386 Packages bdmurray@clean-xenial-amd64:~$ apt-cache policy apt apt: Installed: 1.2.25~rbalint2 Candidate: 1.2.25~rbalint2 Version table: *** 1.2.25~rbalint2 500 500 http://ppa.launchpad.net/rbalint/scratch/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 1.2.20 500 500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages 1.2.15ubuntu0.2 500 500 http://192.168.10.7/ubuntu xenial-security/main amd64 Packages 1.2.10ubuntu1 500 500 http://192.168.10.7/ubuntu xenial/main amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Brian: did you have the updated apt 1.2.25~rbalint2 package installed, too? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Additionally, when I modified my reboot script to reboot when linux- headers were half-installed I ran into the following: bdmurray@clean-xenial-amd64:~$ sudo apt-get dist-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. I thought that is what we are trying to avoid. Here's the script: bdmurray@clean-xenial-amd64:~$ cat u-u-reboot.sh #!/bin/sh loop=1 count=0 today=$(date +%Y-%m-%d) while [ $loop -gt 0 ] do count=$(expr $count + 1) echo "loop...$count" time=$(date +%H:%M) if [ $(grep -r -e "$today $time.*status half-installed linux-headers.*" /var/log/dpkg.log | wc -l) -ge 1 ]; then aplay /usr/share/sounds/alsa/Front_Right.wav sudo reboot fi sleep 1 done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
So far this seems to work, I don't get an inconsistent system while
testing on Ubuntu 16.04, I did notice a crash report in /var/crash from
unattended-upgrades. Here's the Traceback:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 918, in do_install
cache, logfile_dpkg, options.verbose or options.debug)
File "/usr/bin/unattended-upgrade", line 433, in upgrade_normal
res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 424, in cache_commit
res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 515, in commit
res = self.install_archives(pm, install_progress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 479, in
install_archives
res = install_progress.run(pm)
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 208, in run
res = self.wait_child()
File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 279, in
wait_child
self.update_interface()
File "/usr/bin/unattended-upgrade", line 227, in update_interface
self._do_verbose_output_if_needed()
File "/usr/bin/unattended-upgrade", line 244, in _do_verbose_output_if_needed
os.write(1, os.read(self.output_logfd, 1024))
OSError: [Errno 5] Input/output error
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1581, in
main(options)
File "/usr/bin/unattended-upgrade", line 1468, in main
logfile_dpkg)
File "/usr/bin/unattended-upgrade", line 921, in do_install
os.write(2, ("Exception: %s\n" % e).encode('utf-8'))
OSError: [Errno 5] Input/output error
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690980
Title:
unattended-upgrades does not block shutdown of system, as it is
designed to
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: apt (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
When InstallOnShutdown is not set u-u is still asked to stop gracefully during download/installation thus all updates may not get installed but the consistency of the system is kept. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Thanks, this happened when Unattended-Upgrade::InstallOnShutdown was set. I have uploaded a new u-u package to the ppa and updated the GitHub PR with the fix. Please give the package a try, it now works fine on my system. I did not notice the issue because the download step was quick in my VM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint unattended-upgrades didn't finish online-update. https://launchpad.net/~rbalint/+archive/ubuntu/scratch/+packages unattended-upgrades: (0.93.2~16.04.0+rbalint2） apt:（1.2.25~rbalint2） Here are logs: /var/log/unattended-upgrades/unattended-upgrades.log 2017-07-26 15:58:59,769 INFO Initial blacklisted packages: 2017-07-26 15:58:59,770 INFO Initial whitelisted packages: 2017-07-26 15:58:59,770 INFO Starting unattended upgrades script 2017-07-26 15:58:59,770 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] 2017-07-26 16:03:53,918 WARNING SIGTERM received, will stop 2017-07-26 16:03:54,073 WARNING SIGTERM received, will stop 2017-07-26 16:03:55,082 WARNING SIGTERM received, will stop /var/log/unattended-upgrades/unattended-upgrades-shutdown.log 2017-07-26 16:03:54,924 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s 2017-07-26 16:04:00,607 INFO - All upgrades installed Installed packages: apt_1.2.25-rbalint2_amd64.deb apt-doc_1.2.25-rbalint2_all.deb apt-transport-https_1.2.25-rbalint2_amd64.deb apt-utils_1.2.25-rbalint2_amd64.deb libapt-inst2.0_1.2.25-rbalint2_amd64.deb libapt-pkg5.0_1.2.25-rbalint2_amd64.deb libapt-pkg-doc_1.2.25-rbalint2_all.deb unattended-upgrades_0.93.2-16.04.0+rbalint2_all.deb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I moved to handling TERM in u-u: https://github.com/rbalint/unattended-upgrades/commits/master I also attached the patch for APT which changes the KillMode and timeout. Since this affects only apt-daily-upgrade.service and it runs "apt.systemd.daily install" which perform minimal tasks when u-u is not installed this should be safe change. I've uploaded apt and u-u for testing to ppa:rbalint/scratch, please give them a try. ** Patch added: "APT change only KillMode and timeout" https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1690980/+attachment/4921242/+files/0001-Kill-only-the-main-process-of-apt-daily-upgrade.serv.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The apport issue seems to be due to a bug in xenial's shared-mime-info: root@xenial-test:/home/rbalint# time apt-get install -y --allow-downgrades --reinstall apport=2.20.1-0ubuntu2 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libllvm3.8 libmircommon5 linux-image-4.4.0-78-generic linux-image-4.4.0-83-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 20 not upgraded. Need to get 0 B/119 kB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 271938 files and directories currently installed.) Preparing to unpack .../apport_2.20.1-0ubuntu2_all.deb ... Unpacking apport (2.20.1-0ubuntu2) over (2.20.1-0ubuntu2) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for systemd (229-4ubuntu18) ... Processing triggers for shared-mime-info (1.5-2ubuntu0.1) ... Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... Processing triggers for man-db (2.7.5-1) ... Setting up apport (2.20.1-0ubuntu2) ... real1m36.802s user0m1.812s sys 0m0.796s root@xenial-test:/home/rbalint# time update-mime-database.real /usr/share/mime real1m53.622s user0m0.264s sys 0m0.096s This takes ~2s on zesty: root@zesty-test:/home/rbalint# time update-mime-database.real /usr/share/mime Unknown media type in type 'all/all' Unknown media type in type 'all/allfiles' real0m2.146s user0m0.272s sys 0m0.104s This may worth further investigation and possibly an SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Julian: OK, I'm changing u-u to handle TERM instead which seems reasonable. Looking at the history it used to use INT, but TERM would be the best choice. The KillMode still needs to be changed. Are you OK with that part? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Julian: OK, I'm changing u-u to handle TERM instead which seems reasonable. Looking at the history it used to use INT, but TERM would be the best choice. The KillMode still needs to be changed. Are you OK with that part? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
apt does not have special handling for USR1, it's the default action, which is TERM. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Julian: Unattended-upgrades exits gracefully on USR1 and apt exits properly, too. Otherwise apt just gets killed on shutdown and without the kill changes u-u gets killed too which is the issue here. If the default KillMode=control-group is kept dpkg gets the signal, too, and u-u can't protect the installation steps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I disagree with the apt patch, well the kill changes. I'm not sure what you're trying to achieve with that, but I definitely don't want to terminate stuff using USR1 and I don't want to only kill the main process (the shell script). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Instead of providing the drop-in and placing it in u-u's preinst I think it would be better to fix apt instead. Apt already exits on SIGUSR1 thus even when u-u is not installed this seems to work correctly. I've uploaded apt and u-u for testing to ppa:rbalint/scratch, please give them a try. Please upgrade apport in advance because the failure seems to be unrelated, but I'm going to check it again. ** Patch added: "Patch against apt" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4920960/+files/0001-Kill-apt-daily-upgrade.service-using-SIGUSR1.patch ** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The new set of commits for u-u are in https://github.com/rbalint /unattended-upgrades/commits/master -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint Something wrong happens when installing deb package apport. (Please check full log as attached) unattended-upgrades-dpkg.log Unpacking python3-apport (2.20.1-0ubuntu2.10) over (2.20.1-0ubuntu2) ... Preparing to unpack .../apport_2.20.1-0ubuntu2.10_all.deb ... unattended-upgrades-shutdown.log 2017-07-25 11:27:46,257 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 38.7177 % (apport) ... 2017-07-25 11:33:12,886 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 38.7177 % (apport) 2017-07-25 11:33:17,906 WARNING - Unattended-upgrade in progress during shutdown, sleeping for 5s Progress: 38.7177 % (apport) 2017-07-25 11:33:22,925 WARNING - Giving up on lockfile after 10 delay //No progress when installing apport. It's always 38.7177 % ** Attachment added: "logs (unattended-upgrades, apt, dpkg, and kern)" https://bugs.launchpad.net/oem-priority/+bug/1690980/+attachment/4920802/+files/log_0725.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I opened a PR upstream with the proposed fix and also prepared a backport for Xenial in this PPA: https://launchpad.net/~rbalint/+archive/ubuntu/scratch The PPA has a build for Artful, too. PR: https://github.com/mvo5/unattended-upgrades/pull/64 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
IMO the proper fix involves several changes which I collected in this GitHub branch to be merged to upstream: https://github.com/rbalint/unattended-upgrades/commits/lock-handling Since the changes are extensive I would prefer merging them upstream, releasing them to sid, then Artful, and then they can be backported to Xenial and other releases. It looks like to me that more code needs to be backported than half of the delta between releases thus I propose SRU-s practically syncing latest unattended-updates to supported releases. Testing of the new code is appreciated, but please let u-u be triggered by the apt-daily* timers because sudo does not protect u-u from being killed as Ethan pointed out in #25. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Brian My test result with Balint's patch is in #22. According to the previous test in #18, the behavior of my test script is different from apt-daily timer. If you want to reproduce this issue, creating override.conf would be a better way. --- sudo cat << EOF > /etc/systemd/system/apt-daily.timer.d/override.conf [Timer] OnCalendar= OnCalendar= *-*-* XX:YY RandomizedDelaySec=1m AccuracySec=1m EOF fi PS: Please remember to modify XX:YY to the time you want. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
I built a new version of unattended-upgrades with Balint's patch and tested it on an Ubuntu 16.04 system. I used the attached modified version of the reboot script provided by Ethan and saw the following in the terminal which I had run "sudo unattended-upgrade --debug --verbose": Preparing to unpack .../libc6-dev_2.23-0ubuntu9_amd64.deb ... Unpacking libc6-dev:amd64 (2.23-0ubuntu9) over (2.23-0ubuntu3) ... Connection to clean-xenial-amd64.local closed by remote host. Connection to clean-xenial-amd64.local closed. The system ended up in a state where I had to run 'sudo dpkg --configure -a' and then 'sudo apt-get -f install'. ** Attachment added: "script to reboot" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4912389/+files/u-u-reboot.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Ethan - Have you tested the patch that Balint provided or are you guessing about how it will behave? If the communication is improved u-u-shutdown will delay the shutdown process while updates are being installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
@Balint The attached patch can fix the communication between u-u and u-u-shutdown. However, without workaround 1 or 2 in #19, u-u will be killed when users reboot/shutdown the device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
The attachment "unattended-upgrades_0.90ubuntu0.7.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
Could you please test the attached patch on Xenial either by rebuilding the package or by grabbing it from https://launchpad.net/~rbalint/+archive/ubuntu/scratch ? It is expected to fix the communication between u-u and u-u-shutdown and make u-u-shutdown wait properly for u-u to finish. ** Patch added: "unattended-upgrades_0.90ubuntu0.7.patch" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1690980/+attachment/4908156/+files/unattended-upgrades_0.90ubuntu0.7.patch ** Changed in: unattended-upgrades (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Changed in: unattended-upgrades (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to
** Summary changed: - No pop-up window to warn users that system should not reboot or shutdown while installing security updates + unattended-upgrades does not block shutdown of system, as it is designed to ** Changed in: unattended-upgrades (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1690980 Title: unattended-upgrades does not block shutdown of system, as it is designed to To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1690980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
