apt (1.2.22) xenial; urgency=medium
[ Julian Andres Klode ]
* Run unattended-upgrade -d in download part
* apt.systemd.daily: Add locking
* Split apt-daily timer into two (LP: #1686470)
[ Matt Kraai ]
* bash-completion: Fix spelling of autoclean (Closes: #861846)
** Changed in: apt (
This bug was fixed in the package apt - 1.4.6~17.04.1
---
apt (1.4.6~17.04.1) zesty; urgency=medium
* apt.systemd.daily: Do not pass -d to unattended-upgrade for the download
job. This actually enables debugging. Instead check if unattended-upgrade
supports an option --download-
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
** Tags removed: regression-proposed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
apt-daily timer r
It was accidentally referenced in the zesty SRU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
apt-daily timer runs at random hours of the day
To manage notifications about this bug
@juliank are you sure? This bug is a won't fix, as this bug requested to
"revert back to doing both update & upgrade at peak time".
I believe no further actions are required on /this/ bug. Or did this bug
# got extra-referenced in some SRU?
--
You received this bug notification because you are a
Changed from verification-failed to verification-needed-zesty so we can
eventually mark this as done when bug 1686470 is verified.
** Tags removed: verification-failed
** Tags added: verification-needed-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Marking it as a duplicate won't actually stop sru-review from processing
the bug and the bug will show up with a line through it on the SRU
report, so I'll just let the tools modify the bug and it can be set to
v-done when bug 1686470 is verified.
--
You received this bug notification because you
The mention is a historic leftover from replacing this one with bug
1686470 - I guess we could just mark this bug as a duplicate of 1686470
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
I see an apt upload in the zesty queue mentioning that it fixes this bug
- should it be dropped from the queue? Or is it some proper fix this
time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615482
done, thanks!
** Changed in: apt (Ubuntu Zesty)
Status: In Progress => 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/1615482
Title:
apt-daily timer runs at random hours of the day
@vorlon Also drop the zesty one from the unapproved queue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
apt-daily timer runs at random hours of the day
To manage notifications about
I have removed the apt SRU from {xenial,yakkety}-proposed per the
preceding comment.
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Won't Fix
** Changed in: apt (Ubuntu Yakkety)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a
Please note this update will be soon superseded by
https://launchpad.net/bugs/1686470
** Tags added: regression-proposed
** Tags added: verification-failed
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hello John, 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.21 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Tes
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Zesty)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Yakkety)
Importance: Undecided
Status: New
** Changed in: apt (Ubuntu Xenial)
Importance: Und
On Tue, Apr 25, 2017 at 08:16:37AM -, Julian Andres Klode wrote:
> We can't increase the delay for older distros, as it delays all daily
> cron jobs there. We could increase to 2 hours, but I don't feel like
> doing daily APT releases changing time outs, and 1.4.1 with the 1 hour
> time out is
OK,
I have now tested this new apt (1.4.1) against the old version (1.4).
My setup is using solely systemd (with no upstart nor cgmanager installed).
I have fast SSD's, so my normal booting time is about 4 seconds.
Now after upgrading to apt 1.4.1 the booting time to GDM increased with about 5
to
Dropping the tag. Boot time can change randomly. Desktop start does
*not* depend on apt timer start, and timer now depends on network-online
in order to actually work. So yes, it actually does something now, so it
is of course slower.
** Tags removed: block-proposed
--
You received this bug noti
This bug was fixed in the package apt - 1.4.1
---
apt (1.4.1) unstable; urgency=medium
[ Julian Andres Klode ]
* systemd: Rework timing and add After=network-online (LP: #1615482)
* debian/rules: Actually invoke dh_clean in override_dh_clean
[ Unit 193 ]
* apt-ftparchive: S
Added the tag: block-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
apt-daily timer runs at random hours of the day
To manage notifications about this bug go to:
https://bug
We can't increase the delay for older distros, as it delays all daily
cron jobs there. We could increase to 2 hours, but I don't feel like
doing daily APT releases changing time outs, and 1.4.1 with the 1 hour
time out is out already.
I mean, I change it to 2 hours now, and tomorrow someone else t
I mean, 1hr is better than the 30min window previously. But since you're
there poking around that bit of code, think we can increase that further
to 2hrs (0500 - 0700)? :D
Also, think we can get the window increase in unattended-upgrades for
older distros (Trusty etc.)?
Thanks for your time!
--
There's usually 3 main windows where the archive servers are under heavy
load. EU, UK/UTC, and US east. The UTC 0630 - 0700 window is usually the
biggest hit.
For the cloud argument, people run CI jobs spinning up new instances in
the cloud. Tools such as cloud-init and juju will normally run apt-
Of course the load will be higher and peakish again, but the period is
twice as long as it was before (it's now 1 hour instead of 30 minutes),
so that should help.
I don't really get the cloud argument, though. APT will run updates on
boot if the instance was running more than 24 hours ago. And re
The attachment "Call apt 5 minutes after system boot for short running
computer" seems to be a patch. If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message perf
Also, I want to point out that when the main archive mirrors are under
heavy load, it doesn't just affect updates but booting up instances,
mostly public clouds, as well since various tools will perform updates
on boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs
The original request to have it randomised over a larger window is as
per LP bug #1554848. As Dimitri points out, many servers and clouds do
not set local timezones so the archive mirrors we run are hit around the
same time saturating the upstream links we have (with users then
reporting issues wit
** Changed in: apt (Ubuntu)
Status: Triaged => 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/1615482
Title:
apt-daily timer runs at random hours of the day
To manage notificati
6 to 7 is the standard time the cron job used to run, so it's basically
reverting to the pre 16.04 (?) status quo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615482
Title:
apt-daily timer runs a
I'm not sure I like the idea of 6am..7am local time.
In case of desktops/laptops they might not be on during that time - we
also do update on boot right?
Many servers and clouds, do not set local timezone, or set it to UTC
explicitely. Ideally we would want to run 6am..7am window based on local
On Fri, Apr 21, 2017 at 06:55:45PM -, Julian Andres Klode wrote:
> While we're at it, we could also push the times 2 hours more outside, to
> 4 and 20. So, something like this would probably be an improvement:
> [Unit]
> Description=Daily apt activities
> After=network.target
>
> [Timer]
> On
While we're at it, we could also push the times 2 hours more outside, to
4 and 20. So, something like this would probably be an improvement:
[Unit]
Description=Daily apt activities
After=network.target
[Timer]
OnCalendar=*-*-* 4,20:00
RandomizedDelaySec=30m
AccuracySec=5m
Persistent=true
[Instal
We can of course add After=network.target but this gives no real guarantee that
internet is available. For waiting with catch up runs during boot, that's
tracked in systemd's bug tracker at
https://github.com/systemd/systemd/issues/5659.
--
You received this bug notification because you are a
I guess we should go to something like
OnCalendar=*-*-* 6,18:00
RandomizedDelaySec=1h
AccuracySec=1h
or tie down random and accuracy even more. We could do like 15 min or so
- the cron job used 30 min sleep maximum.
The boot argument with short runtime should be ignored. We can't help
everyone.
** Changed in: apt (Ubuntu)
Milestone: None => ubuntu-17.10
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
I was able to override it using /etc/systemd/system/apt-
daily.timer.d/override.conf with this config:
###
[Timer]
OnCalendar=
OnCalendar=*-*-* 02:00
RandomizedDelaySec=4h
AccuracySec=1m
Persistent=true
###
Which Means:
OnCalendar | Any day *-*-* at 02:00hrs. NOTE: See the first empty
According to https://ubuntuforums.org/showthread.php?t=2330407&page=2 I
am not the only user, where the package list is never updated due to the
default timer setting in /etc/systemd/system/timers.target.wants/apt-
daily.timer . This way, the Taskbar-GUI App never displays any available
package upd
Marking this 'high' and a regression. This had been deliberately
engineered in Ubuntu to run once per day outside of normal work hours,
with a random offset <1h to spread out the mirror load. The current
behavior is not consistent with that design, and can be disruptive to
the regular use of the
Marking this 'high' and a regression. This had been deliberately
engineered in Ubuntu to run once per day outside of normal work hours,
with a random offset <1h to spread out the mirror load. The current
behavior is not consistent with that design, and can be disruptive to
the regular use of the
I came to the conclusion that to manually control unattended upgrades it
currently the "easiest" (sarcasm tag on) way to only let the timer
update your package list and manually run unattended-upgrades via cron
at your desired time.
To do so:
# apt-get install unattended-upgrades update-notifier-
My attempt to restrict unattended reboots to times between 0 and 6 AM
wasn't successful. What I did is I created a /etc/systemd/system/apt-
daily.timer.d/override.conf with the following contents:
[Timer]
OnCalendar=*-*-* 00:00
RandomizedDelaySec=6h
unattended-upgrade ran and reboote
Separating out u-u from the rest of the apt maintenance script could be
useful, but I prefer running the update, package fetch, upgrade then
cache clean up all in one hit. You *can* delay your reboot time, but the
shutdown command, at least pre-systemd would run until the shutdown
happens, periodic
** Tags added: xenial
** 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/1615482
Title:
apt-daily timer runs at random hours of the day
To manage notifications about this
Fun story: unattended-upgrades upgraded docker-engine in the middle of a
day, breaking gitlab CI builds until a sysadmin figured out what
happened and rebooted the machine manually.
unattended-upgrades has an option to postpone unattended reboots to some
safer time (like 2AM). Perhaps a similar o
Right, I understand this argument. We should think about this a bit
more.
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
** Changed in: apt (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
45 matches
Mail list logo
