This bug was fixed in the package unattended-upgrades - 0.92ubuntu1.2
---
unattended-upgrades (0.92ubuntu1.2) yakkety; urgency=medium
* Ensure that network and local filesystems are available when running
unattended-upgrades during shutdown mode. (LP: #1618900)
-- Brian Murray
This bug was fixed in the package unattended-upgrades - 0.90ubuntu0.3
---
unattended-upgrades (0.90ubuntu0.3) xenial-proposed; urgency=medium
* Ensure that network and local filesystems are available when running
unattended-upgrades during shutdown mode. (LP: #1618900)
-- Bria
2016-12-20 11:01:59,325 INFO Starting unattended upgrades script
2016-12-20 11:01:59,326 INFO Allowed origins are: ['o=Ubuntu,a=xenial',
'o=Ubuntu,a=xenial-security']
2016-12-20 11:04:43,551 INFO Packages that will be upgraded: apport apport-gtk
apt apt-transport-https apt-utils bind9-host cpp-5
verification-done for yakkety:
2016-12-20 10:41:41,532 INFO Starting unattended upgrades script
2016-12-20 10:41:41,532 INFO Allowed origins are: ['o=Ubuntu,a=yakkety',
'o=Ubuntu,a=yakkety-security']
2016-12-20 10:43:35,014 INFO Packages that will be upgraded: apport apport-gtk
apt apt-transport
Hello Guillaume, or anyone else affected,
Accepted unattended-upgrades into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/0.92ubuntu1.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this
** Description changed:
+ [Impact]
+ There are some race conditions in unattended-upgrades when it is used in
shutdown mode. It is possible that the network has already been brought down or
for a local file system, like /var/, to be unmounted before the
unattended-upgrades script is run. This
I want to write a test case for this SRU, where did you see the error
messages that appear in the bug description? Were they in /var/log
/unattended-upgrades/unattended-upgrades.log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Sorry, I read the code and see that it is producing those messages.
unattended-upgrade:print(_("An error occurred: '%s'") %
item.error_text)
unattended-upgrade:logging.error(_("An error occurred: '%s'"),
item.error_text)
Binary file unattended-upgrade.pyc matches
** Changed in: unattended-upgrades (Ubuntu Yakkety)
Milestone: None => yakkety-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618900
Title:
[Xenial/0.90] Systemd dependencies issues when
** Changed in: unattended-upgrades (Ubuntu Xenial)
Assignee: (unassigned) => Brian Murray (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/1618900
Title:
[Xenial/0.90] Systemd depen
This should be fixed in Zesty now:
unattended-upgrades (0.93.1) unstable; urgency=medium
[ Brian Murray ]
* Create logfile_dpkg if it doesn't exist
* Make sure the statedir exists too
* ensure network and local-fs are available in shutdown
...
-- Michael Vogt Sun, 11 Dec 2016 11:31:26 +
** Changed in: unattended-upgrades (Ubuntu)
Milestone: None => ubuntu-17.02
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618900
Title:
[Xenial/0.90] Systemd dependencies issues when used in "S
** Changed in: unattended-upgrades (Ubuntu)
Assignee: (unassigned) => Brian Murray (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/1618900
Title:
[Xenial/0.90] Systemd dependencies
I've created an upstream pull request with these fixes.
https://github.com/mvo5/unattended-upgrades/pull/38
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618900
Title:
[Xenial/0.90] Systemd depend
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618900
Title:
[Xenial/0.90] Systemd dependencies issues when used in "S
Before=local-fs.target would be needed for the mountpoints like /boot.
** Tags added: rls-z-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618900
Title:
[Xenial/0.90] Systemd dependencies
If a unit needs to get stopped before the network gets stopped, you
shold add "After=network.target". (See man systemd.special).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618900
Title:
[Xenial/
Oh, actually not -- that would be for a service which gets *stopped*
during shutdown (i. e. the usual way). If you want to *start* on
shutdown, you need to be Before=network.target.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
The service possibly needs a relationship with the network service.
[Unit]
Description=Unattended Upgrades Shutdown
DefaultDependencies=no
Before=shutdown.target reboot.target halt.target
Documentation=man:unattended-upgrade(8)
[Service]
Type=oneshot
ExecStart=/usr/share/unattended-upgrades/unatt
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1618900
Title:
[Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"
To manage notifications about this bug go t
20 matches
Mail list logo