public inbox for pve-user@lists.proxmox.com
 help / color / mirror / Atom feed
* [PVE-User] Edit: Boot Order mask
@ 2021-04-13  8:05 Piviul
  2021-04-13  8:57 ` Alain Péan
  2021-04-16 14:16 ` Piviul
  0 siblings, 2 replies; 6+ messages in thread
From: Piviul @ 2021-04-13  8:05 UTC (permalink / raw)
  To: Proxmox VE user list

I ask[¹] about this little problem on the forum but nobody found a 
solution, so I try here...

In my PVE the mask where I can change the Boot Order options of a VM is 
not ever the same. If I access to the mask from 2 nodes (say node1 and 
node2) the mask is a simple html form with only combo boxes. On the 
third node (say node3) the mask is more sophisticated, can support the 
drag and drop, has checkbox... in other word it's different. So I would 
like to know why my three nodes doesn't have the same mask even if they 
are at the same proxmox version and if there is a way that all nodes 
shows the same mask.

I ask you because this is not only a layout problem; if I modify the 
boot order options from the node3, I can see strange chars in the PVE 
gui of the other two nodes but if I configure the boot order options 
from node1 or node2 all seems works flawless.

Best regards

Piviul

[¹] 
https://forum.proxmox.com/threads/strange-chars-in-boot-order-options.87169/







^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PVE-User] Edit: Boot Order mask
  2021-04-13  8:05 [PVE-User] Edit: Boot Order mask Piviul
@ 2021-04-13  8:57 ` Alain Péan
  2021-04-14  7:37   ` Piviul
  2021-04-16 14:16 ` Piviul
  1 sibling, 1 reply; 6+ messages in thread
From: Alain Péan @ 2021-04-13  8:57 UTC (permalink / raw)
  To: pve-user

Le 13/04/2021 à 10:05, Piviul a écrit :
> I ask[¹] about this little problem on the forum but nobody found a 
> solution, so I try here...
>
> In my PVE the mask where I can change the Boot Order options of a VM 
> is not ever the same. If I access to the mask from 2 nodes (say node1 
> and node2) the mask is a simple html form with only combo boxes. On 
> the third node (say node3) the mask is more sophisticated, can support 
> the drag and drop, has checkbox... in other word it's different. So I 
> would like to know why my three nodes doesn't have the same mask even 
> if they are at the same proxmox version and if there is a way that all 
> nodes shows the same mask.
>
> I ask you because this is not only a layout problem; if I modify the 
> boot order options from the node3, I can see strange chars in the PVE 
> gui of the other two nodes but if I configure the boot order options 
> from node1 or node2 all seems works flawless. 

Hi Piviul,

My guess would be that your nodes would have different versions of 
Proxmox packages. And not the same proxmox interface on each...

The best thing would be to have the complete version of each package 
wich 'pveversion -v', but a shorter first information is to display, and 
copy paste just version here ?
# pveversion

Thanks

Alain

-- 
Administrateur Système/Réseau
C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
Boulevard Thomas Gobert (ex Avenue de La Vauve), 91120 Palaiseau
Tel : 01-70-27-06-88 Bureau A255




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PVE-User] Edit: Boot Order mask
  2021-04-13  8:57 ` Alain Péan
@ 2021-04-14  7:37   ` Piviul
  2021-04-14 16:15     ` Alain Péan
  0 siblings, 1 reply; 6+ messages in thread
From: Piviul @ 2021-04-14  7:37 UTC (permalink / raw)
  To: pve-user

[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]

Il 13/04/21 10:57, Alain Péan ha scritto:
> Hi Piviul,
>
> My guess would be that your nodes would have different versions of 
> Proxmox packages. And not the same proxmox interface on each...
>
> The best thing would be to have the complete version of each package 
> wich 'pveversion -v', but a shorter first information is to display, 
> and copy paste just version here ?
> # pveversion
>
> Thanks

I Alain, first of all thank you very much indeed to you and to all 
people answered this thread. I reply your message but the infos here 
should answer even the infos asked from Alwin...

I send directly the output differences from the command pveversion with 
-v flag because all three nodes show the same 
"pve-manager/6.3-6/2184247e (running kernel: 5.4.106-1-pve)" version.

So I have launched the following command in all three nodes:

# pveversion -v > pveversion.$(hostname)

obtaining 3 differents files and I've done the diff between the first 
two files (referring to pve01 and pve02) and as expected there is no 
difference:

$ diff pveversion.pve0{1,2}

Then I have done the diff between the first and the third node and this 
is the result:

$ diff pveversion.pve0{1,3}
5d4
< pve-kernel-5.3: 6.1-6
8,9c7
< pve-kernel-5.3.18-3-pve: 5.3.18-3
< pve-kernel-5.3.10-1-pve: 5.3.10-1
---
 > pve-kernel-5.4.34-1-pve: 5.4.34-2

there are some little differences yes but in kernel that are not in use 
any more (in all 3 nodes uname -r shows 5.4.106-1-pve)...

Attached you can find all three files hoping the system doesn't cut them.

Please can I ask you if you have a 6.3 node in your installations that 
was previously in 6.2 version (i.e. not installed directly in 6.3 
version)? Can you tell me if the "Boot order" musk is the one with only 
combo boxes or the more evoluted drag and drop musk?

Thank you very much

Piviul



[-- Attachment #2: pveversion.pve01 --]
[-- Type: text/plain, Size: 1297 bytes --]

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

[-- Attachment #3: pveversion.pve02 --]
[-- Type: text/plain, Size: 1297 bytes --]

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

[-- Attachment #4: pveversion.pve03 --]
[-- Type: text/plain, Size: 1241 bytes --]

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PVE-User] Edit: Boot Order mask
  2021-04-14  7:37   ` Piviul
@ 2021-04-14 16:15     ` Alain Péan
  2021-04-15 14:03       ` Piviul
  0 siblings, 1 reply; 6+ messages in thread
From: Alain Péan @ 2021-04-14 16:15 UTC (permalink / raw)
  To: pve-user

Le 14/04/2021 à 09:37, Piviul a écrit :
> I Alain, first of all thank you very much indeed to you and to all 
> people answered this thread. I reply your message but the infos here 
> should answer even the infos asked from Alwin...
>
> I send directly the output differences from the command pveversion 
> with -v flag because all three nodes show the same 
> "pve-manager/6.3-6/2184247e (running kernel: 5.4.106-1-pve)" version.
>
> So I have launched the following command in all three nodes:
>
> # pveversion -v > pveversion.$(hostname)
>
> obtaining 3 differents files and I've done the diff between the first 
> two files (referring to pve01 and pve02) and as expected there is no 
> difference:
>
> $ diff pveversion.pve0{1,2}
>
> Then I have done the diff between the first and the third node and 
> this is the result:
>
> $ diff pveversion.pve0{1,3}
> 5d4
> < pve-kernel-5.3: 6.1-6
> 8,9c7
> < pve-kernel-5.3.18-3-pve: 5.3.18-3
> < pve-kernel-5.3.10-1-pve: 5.3.10-1
> ---
> > pve-kernel-5.4.34-1-pve: 5.4.34-2
>
> there are some little differences yes but in kernel that are not in 
> use any more (in all 3 nodes uname -r shows 5.4.106-1-pve)...
>
> Attached you can find all three files hoping the system doesn't cut them.
>
> Please can I ask you if you have a 6.3 node in your installations that 
> was previously in 6.2 version (i.e. not installed directly in 6.3 
> version)? Can you tell me if the "Boot order" musk is the one with 
> only combo boxes or the more evoluted drag and drop musk?

Hi Piviul,

I don't think only a difference in kernel could explain this difference 
in the web interface, if the other packages are the same. Did you try to 
clear the cache in your web browsers ?

The attached files are indeed there. I looked at the versions, and all 
three appears up to date, so for me, the only origin that I can suppose 
could be the browser cache.

Alain

-- 
Administrateur Système/Réseau
C2N Centre de Nanosciences et Nanotechnologies (UMR 9001)
Boulevard Thomas Gobert (ex Avenue de La Vauve), 91120 Palaiseau
Tel : 01-70-27-06-88 Bureau A255




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PVE-User] Edit: Boot Order mask
  2021-04-14 16:15     ` Alain Péan
@ 2021-04-15 14:03       ` Piviul
  0 siblings, 0 replies; 6+ messages in thread
From: Piviul @ 2021-04-15 14:03 UTC (permalink / raw)
  To: pve-user

Il 14/04/21 18:15, Alain Péan ha scritto:
> Hi Piviul,
>
> I don't think only a difference in kernel could explain this 
> difference in the web interface, if the other packages are the same. 
> Did you try to clear the cache in your web browsers ?
>
> The attached files are indeed there. I looked at the versions, and all 
> three appears up to date, so for me, the only origin that I can 
> suppose could be the browser cache.

But I'm sure it's not a cache browser because I have clear the cache and 
I have tested this problem in different browsers in different PCs... in 
my opinion there is a bug: during the node upgrade to 6.3, proxmox VE 
doesn't update the code that generate the Boot order option mask. Please 
can you verify if in your 6.3 proxomox nodes that are updates from 
previously 6.2 you can see the new drag and drop boot order mask?

Thank you very much

Piviul





^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PVE-User] Edit: Boot Order mask
  2021-04-13  8:05 [PVE-User] Edit: Boot Order mask Piviul
  2021-04-13  8:57 ` Alain Péan
@ 2021-04-16 14:16 ` Piviul
  1 sibling, 0 replies; 6+ messages in thread
From: Piviul @ 2021-04-16 14:16 UTC (permalink / raw)
  To: pve-user

Il 13/04/21 10:05, Piviul ha scritto:
> I ask[¹] about this little problem on the forum but nobody found a 
> solution, so I try here...
>
> In my PVE the mask where I can change the Boot Order options of a VM 
> is not ever the same. If I access to the mask from 2 nodes (say node1 
> and node2) the mask is a simple html form with only combo boxes. On 
> the third node (say node3) the mask is more sophisticated, can support 
> the drag and drop, has checkbox... in other word it's different. So I 
> would like to know why my three nodes doesn't have the same mask even 
> if they are at the same proxmox version and if there is a way that all 
> nodes shows the same mask.
>
> I ask you because this is not only a layout problem; if I modify the 
> boot order options from the node3, I can see strange chars in the PVE 
> gui of the other two nodes but if I configure the boot order options 
> from node1 or node2 all seems works flawless.

The problem has been solved reinstalling pve-manager with the command

# apt install --reinstall pve-manager

|Thank you very much to all list members Have a great day! Piviul |
||

||



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-04-16 14:17 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-13  8:05 [PVE-User] Edit: Boot Order mask Piviul
2021-04-13  8:57 ` Alain Péan
2021-04-14  7:37   ` Piviul
2021-04-14 16:15     ` Alain Péan
2021-04-15 14:03       ` Piviul
2021-04-16 14:16 ` Piviul

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal