This is happening in juju 3.1.2 deploying KVMs on top of an LXD clusters.
# Steps to reproduce:
1. Add machine
juju add-machine --constraints="virt-type=virtual-machine mem=4G cores=4 root-disk=40G root-disk-source=remote" --base ubuntu@22.04
2. When machine is ready deploy Microk8s on it with:
juju add-unit microk8s --to <id-of-the-machine>
# Expected result:
Unit starts installing on the machine
# Actual result:
Machine goes to error state with message:
19 error 172.16.0.16 juju-657122-19 ubuntu@22.04 cannot upgrade machine's lxd profile: update failed: Key "linux.kernel_modules" cannot be updated when VM is running
# Workaround:
Stop the VM and then start with:
lxc stop --force juju-657122-19 lxc start juju-657122-19
and machine will no longer be in error state and once the KVM is running again unit will start installing on it.
This is happening in juju 3.1.2 deploying KVMs on top of an LXD clusters.
# Steps to reproduce:
1. Add machine
juju add-machine --constraints= "virt-type= virtual- machine mem=4G cores=4 root-disk=40G root-disk- source= remote" --base ubuntu@22.04
2. When machine is ready deploy Microk8s on it with:
juju add-unit microk8s --to <id-of-the-machine>
# Expected result:
Unit starts installing on the machine
# Actual result:
Machine goes to error state with message:
19 error 172.16.0.16 juju-657122-19 ubuntu@22.04 cannot upgrade machine's lxd profile: update failed: Key "linux. kernel_ modules" cannot be updated when VM is running
# Workaround:
Stop the VM and then start with:
lxc stop --force juju-657122-19
lxc start juju-657122-19
and machine will no longer be in error state and once the KVM is running again unit will start installing on it.