Gabriele Baldoni

It seems that multiple rebase messed up and touched files that were not supposed to be touched. So I'll do a new PR, with less mess in the commits/rebase. I'll...

Hi @heyong4725, I had indeed a very similar issue, the cause was an old plugin causing the crash. I see this line in your log `Plugin storages loaded from /usr/lib/libzplugin_storages.so`...

Hi @ajkavanagh I'm using lxd version 3.2 and pylxd 2.2.4 on Xenial I think I have to update to fix this

Thanks @ajkavanagh Now I see the migration starting but then I got an error on the websockets: ``` Traceback (most recent call last): File "migration.py", line 13, in cont.migrate(client_remote,wait=True) File...

Thanks @ajkavanagh the version of LXD is the same in both servers (3.2) installed using snap same as pylxd which is version 2.2.6 on both, I can try using different...

@ajkavanagh I have found I way to make this work, I have to use the correct ip address also when connecting to the source node, the address should be reachable...

@ajkavanagh Even if the migration works I got this error: ``` Traceback (most recent call last): File "migration.py", line 13, in cont.migrate(client_remote,wait=True) File "/usr/local/lib/python3.5/dist-packages/pylxd/models/container.py", line 426, in migrate self.generate_migration_data(), wait=wait)...

Thank you @antoineco I indeed added that parameter and now it works.

This is still relevant to the new rust codebase. In this case, the problem comes from `nix` and `psutil` crates. We should avoid them in the agent

A possible solution is to have three storages in each node. - `/fos/global/**` for global system information, such as Accounts, Catalog, and Instances - `/fos/local/public//**` for node information that is...