Comment 14 for bug 1904599

> My gut feeling is that this happens due to unfortunate timing of the leader changing.

Bas, is this on a very resource-constrained set of hardware? I'm wondering why leadership would change during a deploy.