[SOLVED] strange chars in boot order options

[piviul]

Hi all, I have 3 proxmox nodes in PVE 6.3-6. 2 nodes are migrated from 6.2 and the third node has been installed directly with the PVE 6.3 version. The first anomaly I found is that the form of the boot order options on the third node (the node 6.3 native) is different from the other two nodes (the ones upgraded from 6.2). Furthermore if I change the boot options from the third node on the first two node I get strange chars like these ones:


How can I solve this little problem?

My best regards

Piviul

 

[Moayad]

Hello,

What is the browser that you are using? is the issue occurs on a different browser?

 

[piviul]

I use firefox but the problem doesn't concern the browser, I have same behavior even in chrome; the problem concern proxmox: the form to manage boot order options in native 6.3 nodes is like this one:

but upgraded pve nodes have this form to manage boot order options:

If I configure the boot order options using a 6.3 node migrated from a previously 6.2 pve version there are no problems but if configure the boot order options from a native 6.3 pve node on the migrated nodes I can see strange chars as shown in the previously message.
This strange behavior doesn't affect the vm concern only the pve gui.

Best regards

piviul

 

[piviul]

Ok I've done a little bit of confusion. I rewrite from scratch the thread.

I have a strange behavior in my 3 nodes PVE. In first two nodes if I want to change the Boot Order Options I get a form like this:


But if I want to change the Boot Order Options from the third node I get this form:


The boot order settings are the same but the interface are not... Furthermore if I change the boot order options from the third node, on the first two nodes I get some strange chars in the boot order options as you can see from this screenshot:


All works as expected if I change the boot order options from one of the first two nodes.

I add that the first two nodes has been migrated from PVE 6.2 but the third nodes was already at the 6.3 version when I added it to the cluster.

I think that during the upgrade something goes wrong on migrating the boot order form didn't it? Any way, can you please help me to have the same boot options form in all cluster nodes?

My best regards

Piviul

 

[Moayad]

Are you use a custom font on your system?
It's works here without any strange chars I tried (Firefox, Chrom, and Chromium)

 

[piviul]

Are you use a custom font on your system?

As far as I know I don't use any custom fonts... for the sake of truth I don't know where and how fonts can be customized.
Any way if you can help me to check it I can check it.

It's works here without any strange chars I tried (Firefox, Chrom, and Chromium)

So do you checked that a PVE 6.3 node migrated from 6.2 shows the same "boot order" mask that a native 6.3 node?
Can I ask you if your PVE node shows the more evoluted drag and drop mask or the basic one with only combo boxes?

So do you think that there is no relation between PVE history versions nodes and this problem of the "Boot Order" mask, didn't you?

Thank you very much

Best regards

Piviul

 

[dcsapak]

my guess is that your browser has cached an older version of the gui, or that one node has a slightly older pve-manager package (can you post the output of pveversion -v of all nodes?)

 

[piviul]

I don't think this problem depend on the cache browser, I have the same behavior in different browsers and clients...
These are the versions:
root@pve01:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph: 14.2.19-pve1
ceph-fuse: 14.2.19-pve1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.13-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-5
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-10
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

root@pve02:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.3: 6.1-6
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.10-1-pve: 5.3.10-1
ceph: 14.2.19-pve1
ceph-fuse: 14.2.19-pve1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.13-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-5
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-10
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

root@pve03:~# pveversion -v
proxmox-ve: 6.3-1 (running kernel: 5.4.106-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-8
pve-kernel-helper: 6.3-8
pve-kernel-5.4.106-1-pve: 5.4.106-1
pve-kernel-5.4.103-1-pve: 5.4.103-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph: 14.2.19-pve1
ceph-fuse: 14.2.19-pve1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: residual config
ifupdown2: 3.0.0-1+pve3
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.8
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-8
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.13-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-9
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-5
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-10
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.4-pve1

The pve03 is the node that have an evoluted version of the mask

Best regards

Piviul

 

[dcsapak]

the behaviour you have (the weird splitting) is because the ui cannot handle the new backend format (order=scsiX,...) this can only happen if the ui loaded is not the current version. and this should only
happen if either the packages are not up to date, or if the browser (or a proxy?) has cached the older version of the ui....

 

[piviul]

Hi Dominik, thank you very much for your reply. I'm sure it is not a cache problem (I have removed the cache and all browsers doesn't matter the OS type and version have the same behavior) so we can argue that depends on different versions of the ui on the nodes... but pveversion says that are all the same version so I'm little bit confused .

As I have previously suggested in my opinion the cause is a bug that during the update of the proxmox from 6.2 to 6.3 didn't update the code of the mask "Boot order".
Can someone please verify if proxmox 6.3 nodes upgraded from previously 6.2 have the new drag and drop mask or mantain the old combo box mask?

Thank you very much!

Piviul

 

[dcsapak]

if you want you can reinstall the relevant package on the relevant node:

apt install --reinstall pve-manager

this will redownload and reinstall the package

 

[piviul]

if you want you can reinstall the relevant package on the relevant node:

apt install --reinstall pve-manager

this will redownload and reinstall the package

Done, that solve my problem. Thank you very much!

Piviul