Hi!
Sorry I don't have a solution, but using "indirect locks" with libvirtd seems
to have no solution when the same cluster also provides the shared filesystem
through cluster means.
(I had reported on that before)
libvirtd cannot start before virtlockd, which annot start before the shared
On Thu, Aug 26, 2021 at 11:13 AM lejeczek via Users
wrote:
> Hi guys.
>
> I sometimes - I think I know when in terms of any pattern -
> get resources stuck on one node (two-node cluster) with
> these in libvirtd's logs:
> ...
> Cannot start job (query, none, none) for domain
> c8kubermaster1;
Hi guys.
I sometimes - I think I know when in terms of any pattern -
get resources stuck on one node (two-node cluster) with
these in libvirtd's logs:
...
Cannot start job (query, none, none) for domain
c8kubermaster1; current job is (modify, none, none) owned by
(192261
