Simon Deziel
Simon Deziel
The additional instrumentation worked as I now got a [longer trace](https://github.com/canonical/lxd/actions/runs/18616723257/job/53082449594?pr=16756#step:18:34461): ``` 0x7f539a4d6584 dqlite_fail src/lib/assert.c:19 0x7f539a4e306f vfsMainFileClose src/vfs.c:1271 0x7f539a5f2c12 ??? ???:0 0x7f539a602f42 ??? ???:0 0x7f539a588c07 ??? ???:0 0x7f539a5f8197 ??? ???:0...
I've hit it again in my fork in the [`clustering_rebalance` test](https://github.com/simondeziel/lxd/actions/runs/19309171892/job/55224954700#step:20:34450): ``` time="2025-11-12T19:33:26Z" level=info msg="Dqlite proxy started" local="100.64.1.103:45018" name=raft remote="100.64.1.102:8443" time="2025-11-12T19:33:26Z" level=info msg="Dqlite connected outbound" local="100.64.1.102:36090" name=raft remote="100.64.1.103:8443" time="2025-11-12T19:33:26Z" level=info...
@wctaylor thanks for the report, I have replicated the issue. FYI, you can temporarily work around it with something along those lines: ``` $ lxc list --columns 4 name=v3 +-----------------------+...
`git rebase -i main` should be all you need to then mark the last commit (`capitalize LXD`) for `fixup`. This will "merge" or "fuse" the 2 commits into one. After...