Closed Lesterpig closed 5 years ago
What do you see if you do:
On host kili
?
Also, can you show lxc config show --expanded <container name>
and lxc storage volume list local
?
Thanks for your help!
lxc config show <container-name> --expanded
architecture: armv7l
config:
boot.autostart.priority: "1"
image.architecture: armhf
image.description: Alpine 3.8 armhf (20181004_13:28)
image.os: Alpine
image.release: "3.8"
image.serial: "20181004_13:28"
limits.memory: 256MB
limits.memory.swap: "false"
volatile.base_image: b1f25d332abc823609988e9b4524e9c016fc8c088249561d3a2fd8e2d2568985
volatile.eth0.host_name: veth7e26223d
volatile.eth0.hwaddr: 00:16:3e:28:17:cd
volatile.idmap.base: "0"
volatile.idmap.current: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.idmap.next: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
volatile.last_state.idmap: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
devices:
eth0:
name: eth0
nictype: bridged
parent: moria2
type: nic
<dev-name>:
path: /mnt
pool: local
source: <dev-name>
type: disk
root:
path: /
pool: local
size: 10GB
type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""
container,<container-name>,,1,kili
custom,<dev-name>,,1,kili
I restarted lxc multiple time, killing remaining processes (lxcfs) when needed, but this completely crashed my cluster: all containers in STOPPED state, unable to start with the aforementioned issue. So, I went the hard way by rebooting all nodes: this solved the issue
So at the end I think snap did not manage to remount the storage pool after upgrade and multiple restarts. Not sure if this is a bug, please close the issue if appropriate. :+1:
Ah, ok, so hopefully this was the mount propagation issue we fixed in the snap packaging a bit over a week ago and now that you've restarted those systems, the mount table makes sense again and things will behave going forward.
Required information
Issue description
After latest snap refresh, trying to start a container is impossible because local storage pools points to invalid directory.
Steps to reproduce
/mnt/pool
<dev-name>
for a container<container-name>
lxc start <container-name>
Information to attach
lxc config show NAME --expanded
)lxc monitor
while reproducing the issue)