Tom Parrott
Tom Parrott
Lets close this for now as we have no reproducer.
Could we store the info as a volatile key?
@simondeziel did you reproduce the error? ``` pytest-cos lxc start cos-bar Error: Failed to handle idmapped storage: No such file or directory: "/var/snap/lxd/common/lxd/storage-pools/default/containers/cos-bar/rootfs" Try `lxc info --show-log cos-bar` for more...
Thanks!
Yes this is exactly what I was seeing after manually loading the kernel modules.
I installed microceph recently and found it to be quite noisy in the logs due to debug mode be enabled by default.
@masnax how this sort of thing achieved in lxd?
Shouldn't schema updates happen first on leader (once dqlite established) and then the nodes move onto per node patches? I believe this is the order its done in lxd, but...
> Wouldn't they always implicitly happen on the leader, as only the leader POSTs to the database? I dont follow you here, the leader surely has direct access to the...
That's correct. That's why I dont understand how the deadlock you're describing is occurring and why there are notifications going on. Also I'm struggling to follow what you mean by...