Code:
proxmox-ve: 4.1-33 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-5 (running version: 4.1-5/f910ef5c)
pve-kernel-4.2.6-1-pve: 4.2.6-33
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-30
qemu-server: 4.0-46
pve-firmware: 1.1-7
libpve-common-perl: 4.0-43
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-21
pve-container: 1.0-37
pve-firewall: 2.0-15
pve-ha-manager: 1.0-18
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
openvswitch-switch: 2.3.2-2For anyone playing along at home, I was using a node name that didn't exist, and carried over "openvz" from 3.x instead of "lxc" for 4.x. So it was a configuration error that was causing the failure.
That said, I'd expect a 404 if requesting a resource that doesn't exist at all -- not a 500 or 501. It took me longer than it should've to track down the issue that was staring me in the face, but I was helped in the wild goose chase by a misleading response from the API.
There are some other quirks about the new API that make it a little challenging to work with, but I'll leave those for another post.
That said, I'd expect a 404 if requesting a resource that doesn't exist at all -- not a 500 or 501. It took me longer than it should've to track down the issue that was staring me in the face, but I was helped in the wild goose chase by a misleading response from the API.
There are some other quirks about the new API that make it a little challenging to work with, but I'll leave those for another post.