[SOLVED] api endpoint rrddata is the same for lxc and qemu

[6uellerbpanda]

I just noticed that when I use following api path (also no error or data null)

qemu/121/rrddata?timeframe=hour&cf=AVERAGE

and

lxc/121/rrddata?timeframe=hour&cf=AVERAGE

it shows the same data

vmid 121 is a lxc container although

but this seems only true for 'rrddata' that both qemu and lxc enpoints are working. I tested it with 'status/current' and 'config' path and this is not working.

is this a bug or done on purpose ?

pveversion -v 
proxmox-ve: 5.1-41 (running kernel: 4.13.13-6-pve) 
pve-manager: 5.1-46 (running version: 5.1-46/ae8241d4) 
pve-kernel-4.13.13-6-pve: 4.13.13-41 
pve-kernel-4.13.13-2-pve: 4.13.13-33 
corosync: 2.4.2-pve3 
criu: 2.11.1-1~bpo90 
glusterfs-client: 3.8.8-1 
ksm-control-daemon: 1.2-2 
libjs-extjs: 6.0.1-2 
libpve-access-control: 5.0-8 
libpve-common-perl: 5.0-28 
libpve-guest-common-perl: 2.0-14 
libpve-http-server-perl: 2.0-8 
libpve-storage-perl: 5.0-17 
libqb0: 1.0.1-1 
lvm2: 2.02.168-pve6 
lxc-pve: 2.1.1-2 
lxcfs: 2.0.8-2 
novnc-pve: 0.6-4 
proxmox-widget-toolkit: 1.0-11 
pve-cluster: 5.0-20 
pve-container: 2.0-19 
pve-docs: 5.1-16 
pve-firewall: 3.0-5 
pve-firmware: 2.0-3 
pve-ha-manager: 2.0-5 
pve-i18n: 1.0-4 
pve-libspice-server1: 0.12.8-3 
pve-qemu-kvm: 2.9.1-9 
pve-xtermjs: 1.0-2 
qemu-server: 5.0-22 
smartmontools: 6.5+svn4324-1 
spiceterm: 3.0-5 
vncterm: 1.5-3 
zfsutils-linux: 0.7.6-pve1~bpo9

 

[dietmar]

I guess it is a bug, but a harmless one.

 

[6uellerbpanda]

I guess it is a bug, but a harmless one.

true

any plans to change this in the future ?
I'm only asking 'cause if the endpoints are the same for both it will be easier to adapt this at my script but if you intend to change it then I will write it already the "correct" way (/lxc/.., /qemu/...) and don't need to fix it later

 

[dietmar]

but if you intend to change it then I will write it already the "correct" way (/lxc/.., /qemu/...) and don't need to fix it later

Yes, please use the 'correct' path.