Hello, I just ran in that bug on a 2.3 proxmox server. It has been fixed (or workarounded) in master by commit 19cec2309dad9487a2fc0a679c1a2b9d9995c4ba It'd be nice to have this fixed properly in 2.3. Thanks.