[SOLVED] GUI message: Unable to parse network options

EllyMae

EllyMae

Member
Jul 20, 2022
133
10
23
After setting (in the GUI) a rate limit of .5 on a network device in the hardware section of a VM, then a subsequent attempt to edit the device throws a message Unable to parse network options

I have not found a way to correct this so that I can edit it again.

PVE version: 8.1.4
 
Hi!

Hmm, I could not reproduce this here on a recent 8.1 PVE.
Can you please post the full version (output of pveversion -v or using the Node -> Summary -> Package Version button).

Posting the config would be also great, ideally the raw file:
cat /etc/pve/qemu-server/VMID.conf (replace VMID with the numerical ID from the broken VM)
 
Here is the config:
Code: 
root@leghorn:/etc/pve/qemu-server# cat 110.conf
#scsi1%3A cryptodata%3A110/vm-110-disk-0.qcow2,backup=0,iothread=1,size=1250G
#scsi2%3A Zvol%3Avm-110-disk-1,backup=0,iothread=1,size=1044G
agent: 1
audio0: device=ich9-intel-hda,driver=spice
balloon: 8192
bios: ovmf
boot: order=scsi0
cores: 4
cpu: host
efidisk0: Zvol:vm-110-disk-0,efitype=4m,pre-enrolled-keys=1,size=1M
machine: q35
memory: 16384
meta: creation-qemu=7.2.0,ctime=1692576549
name: bullwinkle
net0: virtio=56:9A:1F:B8:B0:9D,bridge=vmbr0,firewall=1,rate=.5
numa: 0
ostype: l26
scsi0: Zvol:vm-110-disk-1,iothread=1,size=50G
scsi1: cryptodata:110/vm-110-disk-0.qcow2,backup=0,iothread=1,size=1250G
scsi2: Zvol:vm-110-disk-2,backup=0,iothread=1,size=1044G
scsihw: virtio-scsi-single
smbios1: uuid=cc54ffc8-5f25-490f-8b50-1c5d30177414
sockets: 1
vga: virtio-gl
vmgenid: 9a775f7d-892d-4001-a6e5-7c9d4ad068be
root@leghorn:/etc/pve/qemu-server#

Here are the versions:
Code: 
proxmox-ve: 8.1.0 (running kernel: 6.5.11-8-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-8
proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve2
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.1
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.4-1
proxmox-backup-file-restore: 3.1.4-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.5
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-4
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.5-3
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1
 
After the reinstall, when I enter .5, the GUI changes it to 0.5, and it works now.
 
That a reinstallation would solve anything seems a bit odd, as this is something that the client would send, not the PVE host transform. And even if such a bug exists, which is naturally a possibility, then a reinstallation should still trigger it (at least if installed with our official ISO and without adding third-party scripts).

While I initially could not reproduce this using Firefox, I now retried with Chromium and there I could see your issue.
But after a bit of additional, it seems that the behavior is not really browser dependent, but depends on how the form gets submitted.
If I click on "OK" to submit, then all floating values without leading digit will expand, e.g., .5 to 0.5, but if I submit through pressing the Enter key, then the .5 will be submitted as is.

The backend actually doesn't care about leading digits, it's just the frontend parser that doesn't expect this.
So I pushed a fix for allowing the UI parser to detect floating values without leading digits before the floating point separator too:
https://git.proxmox.com/?p=pve-manager.git;a=commitdiff;h=b120875cc4339b7c9358fe8019817f60960e7edf
 
You must log in or register to reply here.
Top Bottom