[SOLVED] All LXC containers grayed out after upgrade to 8.3

[EmilioMoreno]

This is a standalone server, no cluster, I am running as my home lab; all the upgrades are done first to this server before going into other environments.
I have just simply upgraded from PVE 8.1 to 8.3 and suddenly all the lxc containers appear like this. Virtual machines are ok and unaffected



If I try to access the containers from the shell I got the following
root@pve-cugat1:~# pct list
can't open '/sys/fs/cgroup/blkio//lxc/104/blkio.throttle.io_service_bytes_recursive' - No such file or directory

root@pve-cugat1:~# pct console 100
lxc-console: 100: ../src/lxc/tools/lxc_console.c: lxc_console_main: 130 100 is not running

root@pve-cugat1:~# pct start 100
root@pve-cugat1:~# pct console 100

Connected to tty 2
Type <Ctrl+a q> to exit the console, <Ctrl+a Ctrl+a> to enter Ctrl+a itself

So it seems they have all powered down. but I can not power them up from the web interface. If I start them from the cli, they start, but still are NOT appearing in the WebUI.
Any ideas?

 

[waltar]

Did you reboot your host after the pve update ? Of not do it.

 

[EmilioMoreno]

@waltar I wanted to avoid rebooting it, as when I do the upgrade in the production cluster I will not have the option to do it unless I migrate all the containers to other servers, but after rebooting, everything went to normal.

Not really a good experience. Until now all the minor upgrades I have done have worked flawlessly and I was expecting this one to behave as well as the others. It is a good thing I do the production upgrade the latest as this will have been a serious issue there. I will avoid upgrading to 8.3 in the other clusters until I have the time to prepara a proper migration.

 

[waltar]

On production cluster it would be better for service availability to use vm's instead of lxc's as the vm's could be migrated without downtime which isn't possible until today with lxc's. Yes ... it took more hw resources (cpu+mem) but anythink is ever ... you have to decide between needed hw usage and it's flexibility.