Parameter verification failed. (400) Error

[psionic]

Seeing this error since upgrading to 6.2 when I try to change CPU resources while Container is running. I have to stop container, change CPU and restart. I didn't have any problem changing CPU resources with 6.1....



Package Versions:
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.34-1-pve: 5.4.34-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-2
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: not correctly installed
ifupdown2: 2.0.1-1+pve8
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

pct config 101
arch: amd64
cores: 48
cpulimit: 20
description: safepay server%0A%0Aafter boot remount Backups%0Azfs mount -O -a%0A
hostname: Safepay
memory: 122880
net0: name=eth0,bridge=vmbr0,firewall=1,gw=192.168.2.1,hwaddr=3A:39:3F:AF2:99,ip=192.168.100.1/16,type=veth
onboot: 0
ostype: ubuntu
rootfs: data:subvol-101-disk-0,size=3300G
swap: 2048
unprivileged: 1

 

[Stoiko Ivanov]

hmm - this could be related to a patch posted today on the pve-devel mailing list
https://pve.proxmox.com/pipermail/pve-devel/2020-May/043575.html

after it gets applied and tested internally a version of pve-container containing it will be made available on the pvetest repository

I hope this helps!

 

[psionic]

hmm - this could be related to a patch posted today on the pve-devel mailing list
https://pve.proxmox.com/pipermail/pve-devel/2020-May/043575.html

after it gets applied and tested internally a version of pve-container containing it will be made available on the pvetest repository

I hope this helps!

Thanks for your response. I look forward to this patch being made available

 

[psionic]

hmm - this could be related to a patch posted today on the pve-devel mailing list
https://pve.proxmox.com/pipermail/pve-devel/2020-May/043575.html

after it gets applied and tested internally a version of pve-container containing it will be made available on the pvetest repository

I hope this helps!

I tested again and the error only happens when the 'CPU limit' parameter is changed while the container is running. There is no error when the 'Cores' parameter is changed while the container is running...