Re: OSTree locking fails sometimes

[Dan Nicholson <nicholson endlessm com>]

On Thu, Jan 24, 2019 at 6:55 AM Colin Walters <walters verbum org> wrote:
> On Thu, Jan 24, 2019, at 7:51 AM, Dan Nicholson wrote:
> > I'd guess that the more likely issue is the recent
> > change to make summary generation take an exclusive lock in
> > https://github.com/ostreedev/ostree/pull/1681
>
> Ooh yes, thanks for that - you are very likely right and I was chasing a red herring.
>
> Which then means...probably the lock timeout should be bumped?  I am uncertain about any hardcoded timeouts 
> really.
>
> But Stefan can you try bumping `lock-timeout-secs` in the repo config?
> See `man ostree.repo-config`

I would also argue that summary generation could be changed to shared
locking as I did in
https://github.com/endlessm/eos-updater/pull/237#issuecomment-425563031.
Then this problem likely goes away unless you're doing concurrent
prunes.