cloud-init-dev team mailing list archive

Thread
Date

Re: [Merge] ~smoser/cloud-init:bug/1693361-apt-get-locks into cloud-init:master

To: Scott Moser <smoser@xxxxxxxxxx>
From: Steve Langasek <steve.langasek@xxxxxxxxxxxxx>
Date: Mon, 12 Jun 2017 19:14:40 -0000
In-reply-to: <20170612182110.8673.33214.launchpad@ackee.canonical.com>
Reply-to: mp+325513@xxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

Review: Needs Information

Would it make more sense logically to be Before=apt-daily.service (the thing that actually takes the conflicting lock), rather than Before=apt-daily.timer?

I don't agree with characterizing this as a "workaround", because even if we had perfect handling of apt locks, we would still care about cloud-init being done *before* apt-daily such that the first boot could finish in a timely manner.

-- 
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/325513
Your team cloud-init commiters is requested to review the proposed merge of ~smoser/cloud-init:bug/1693361-apt-get-locks into cloud-init:master.