Hello,
I'm running some proxmox nodes and wrote my own webinterface (php) to manage my virtual servers.
For this, I'm using the proxmox class of saleh7 on GITHub (https://github.com/Saleh7/ProxmoxVE_PHP_API).
To set nesting for id 100 (lxc container):
But the nesting feature isn't set and also not waiting for restart (pending).
I've tested a few things to exclude an error of the class:
With this both tests I've excluded the php class as point of failure. In my opinion, the proxmox api is returning the correct errors for the wrong values, so the submitted values within "Test 1" are interpreted correctly by the proxmox api and should be applied.
For whatever reason, the "features" aren't applied by the api.
Notice:
On shell
is working fine!
Setting these value within the proxmox webgui is working fine too.
Any ideas?
I'm running some proxmox nodes and wrote my own webinterface (php) to manage my virtual servers.
For this, I'm using the proxmox class of saleh7 on GITHub (https://github.com/Saleh7/ProxmoxVE_PHP_API).
To set nesting for id 100 (lxc container):
PHP:
# Test 1
$this->nodes->setLxcConfig("node1", "100", array("features" => "nesting=1"));
#Result is:
object(stdClass)#43 (1) { ["data"]=> NULL }But the nesting feature isn't set and also not waiting for restart (pending).
I've tested a few things to exclude an error of the class:
PHP:
## Test 2 set nesting to 5 instead of 0|1
$this->nodes->setLxcConfig("node1", "100", array("features" => "nesting=5"));
# Result:
object(stdClass)#54 (2) { ["errors"]=> object(stdClass)#43 (1) { ["features"]=> string(88) "invalid format - format error features.nesting: type check ('boolean') failed - got '5' " } ["data"]=> NULL }
## Test 3 --> set Nesting instead of nesting
$this->nodes->setLxcConfig("node1", "100", array("features" => "Nesting=1"));
# Result:
object(stdClass)#43 (2) { ["data"]=> NULL ["errors"]=> object(stdClass)#54 (1) { ["features"]=> string(134) "invalid format - format error features.Nesting: property is not defined in schema and the schema does not allow additional properties " } }With this both tests I've excluded the php class as point of failure. In my opinion, the proxmox api is returning the correct errors for the wrong values, so the submitted values within "Test 1" are interpreted correctly by the proxmox api and should be applied.
For whatever reason, the "features" aren't applied by the api.
Notice:
On shell
Bash:
pvesh set /nodes/node1/lxc/100/config -features "nesting=1"Setting these value within the proxmox webgui is working fine too.
Any ideas?
Code:
Using: Debian 11
Version overview:
proxmox-ve: 7.1-1 (running kernel: 5.13.19-2-pve)
pve-manager: 7.1-8 (running version: 7.1-8/5b267f33)
pve-kernel-helper: 7.1-6
pve-kernel-5.13: 7.1-5
pve-kernel-5.4: 6.4-11
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.157-1-pve: 5.4.157-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.0
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-5
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.0-14
libpve-guest-common-perl: 4.0-3
libpve-http-server-perl: 4.0-4
libpve-storage-perl: 7.0-15
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.11-1
lxcfs: 4.0.11-pve1
novnc-pve: 1.3.0-1
proxmox-backup-client: 2.1.2-1
proxmox-backup-file-restore: 2.1.2-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-4
pve-cluster: 7.1-3
pve-container: 4.1-3
pve-docs: 7.1-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.3-4
pve-ha-manager: 3.3-1
pve-i18n: 2.6-2
pve-qemu-kvm: 6.1.0-3
pve-xtermjs: 4.12.0-1
qemu-server: 7.1-4
smartmontools: 7.2-pve2
spiceterm: 3.2-2
swtpm: 0.7.0~rc1+2
vncterm: 1.7-1
zfsutils-linux: 2.1.1-pve3
Last edited:
)