[Expired for apt (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apt (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711428
On Thu, Aug 17, 2017 at 07:59:00PM -, Jim Browne wrote:
> However, is juliank's note about the implementation of After= a concern
> w.r.t. how LP#1693361 was resovled?
I don't think so. He's correct that the ordering doesn't guarantee that we
don't hit a conflict if the units wrap around and
> So I think this is something that you will want to fix in your image
> mastering scripts.
I agree and am fine with this being marked INVALID.
However, is juliank's note about the implementation of After= a concern
w.r.t. how LP#1693361 was resovled?
--
You received this bug notification
On Thu, Aug 17, 2017 at 07:20:20PM -, Jim Browne wrote:
> Hmmm. I confirm what you see.
> I think this problem is arising because we have Packer run (due to
> LP#1693361):
> systemctl disable apt-daily.service
> systemctl disable apt-daily.timer
> when building the AMI.
> I guess
Not that if B has After=A does not imply that the two don't run at the
same time. If B is already running, A will be started as well. That's
the reason why we added a lock file in apt:
if [ "$1" = "lock_is_held" ]; then
shift
else
# Maintain a lock on fd 3, so we can't run the script
Hmmm. I confirm what you see.
I think this problem is arising because we have Packer run (due to LP#1693361):
systemctl disable apt-daily.service
systemctl disable apt-daily.timer
when building the AMI.
I guess if apt-daily.service is disabled the Before is not transitive
from
The apt-daily-upgrade service already declares itself to be 'After=apt-
daily.service'. So there should be strict sequencing here of cloud-
final.service -> apt-daily.service -> apt-daily-upgrade.service. If
that's not happening, this warrants analysis to understand why so that
it can be fixed
