Is there a way to migrate v2.0.11 config to v3.0.0?

1

I’m keeping the whole /var/lib/lxd in a separate LVM volume.

Just now I’ve installed an ubuntu bionic (18.04) on the machine that was previously running ubuntu xenial (16.04)

Now I have the lxd v3.0.0 which is not compatible with the old v2.0.11 config format

May 07 14:47:43 <redacted> lxd[719]: key=core.proxy_http lvl=eror msg="Invalid configuration key: unknown key" t=2018-05-07T14:47:43+1200
May 07 14:47:43 <redacted> lxd[719]: key=core.proxy_https lvl=eror msg="Invalid configuration key: unknown key" t=2018-05-07T14:47:43+1200
May 07 14:47:43 <redacted> lxd[719]: key=storage.lvm_thinpool_name lvl=eror msg="Invalid configuration key: unknown key" t=2018-05-07T14:47:43+1200
May 07 14:47:43 <redacted> lxd[719]: key=storage.lvm_vg_name lvl=eror msg="Invalid configuration key: unknown key" t=2018-05-07T14:47:43+1200
May 07 14:47:43 <redacted> lxd[719]: key=storage.lvm_volume_size lvl=eror msg="Invalid configuration key: unknown key" t=2018-05-07T14:47:43+1200

Is there a script or some other official way to migrate the config and keep already existing containers?

I tried to search myself, but a “migrate” term in the codebase and documentation collides with with what I’m looking for.

Is this kind of “upgrade” possible at all? (I mean, are there some other possible breaking changes?)

2

On first startup of LXD post-upgrade, the upgrade code should have run, migrating you to the new storage pools and networks format and converting your database as well.

It’s possible that some of those errors will show up right before the upgrade but things should then be fine afterwards.

The log above misses a lot of context to figure out what’s happening. It’s unclear whether it’s startup output or just errors being sent back to a client tool trying to set the now deprecated keys.

3

Yep, somehow I triggered the migration later (manually though, the automatic migration did not succeed). But then I found the migrated containers had the wrong uid mappings, so I decided to make a clean install and migrate everything between the servers instead.