Can't create VMs in PVE-9.1.6

A

andreisrr

Member
Feb 2, 2024
59
7
13
I can no longer able to create a VM in PVE-9.1.6 with root user.
(I was trying to set up a more complex set of permissions, but in the end not even Administrator worked)
When I go through the VM creation wizard, when I get to the final "Confirm" tab, the UI breaks.
I still get a "next" button, lower right, but it doesn't work.
Confirm tab has empty screen, and apparently activates "Network" tab.
Going back and forth through tabs, I get "Finish" button in the lower left in place of Help button, still not functional.
After closing this non-working wizard, part of the UI seem broken, until I force a full page reload.

This is the error I get in the browser console:
Code: 
Uncaught TypeError: deleteSet.keys().toArray is not a function
    onGetValues https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:54855
    getValues https://10.106.50.149:8006/proxmoxlib.js?ver=v5.1.8-t1772102916:8027
    getValues https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:23697
    getValues https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:23696
    show https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:52118

Last time I was able to create VMs successfully, using same browser, was on feb 11th. Since then a few package updates have been applied to PVE so that now it shows 9.1.6. IIRC it showed a slightly older version then, 9.x generation though.

Firefox ESR-115, latest update 3 days ago. Company set browser, can't change.
Please help.
 
Last edited:
I retraced my steps, reloaded UI, tried to create a VM with browser console open. Only at the last step, when getting to "Confirm" tab, I get this

Code: 
Uncaught TypeError: deleteSet.keys().toArray is not a function
    onGetValues https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:54855
    getValues https://10.106.50.149:8006/proxmoxlib.js?ver=v5.1.8-t1772102916:8027
    getValues https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:23697
    getValues https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:23696
    show https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:52118
    ExtJS 43
    initComponent https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:67573
    callParent ExtJS
    initComponent https://10.106.50.149:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:68060
    ExtJS 4
    <anonymous> https://10.106.50.149:8006/#v1:0:=node/pve1:4:::::::6:45
    ExtJS 15

I navigated the PVE Manager UI as much as I could, this is the only place I get errors in the browser console.

Note: the CT creation wizard does not seem to be affected.
 
Hi @andreisrr , I was about to ask whether you backed out everything you changed and now it sounds like you did?

I'd recommend doing a few sanity checks:
a) try to create a VM with QM
b) try to create with "pvesh" via API
c) try to create a VM with "curl" using an equivalent json request

Is this a cluster? If it is, are all nodes experiencing the same issue?
Is there anything interesting in the log for this command? debsums -ca 2>&1 | tee /var/log/debsums-audit.log
Have you installed any enhancing scripts?

Are all packages up to date?
Finally, you can reinstall GUI portion to ensure there is nothing missing there:
apt install --reinstall pve-manager proxmox-widget-toolkit libjs-extjs

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: weehooey-ch
Did you use helper scripts? Also try pveupdate && pveupgrade.
 
a) Haven't tried yet the command line. So far it seems a browser related problem with JS and I pursued the matter as such.
b) and c) are too advanced for my knowledge, yet
Yes, it is a cluster, 4 nodes. Yes, all nodes are at same version, updated yesterday, so all packages are up to date.
Yes, same problem, regardless of what node I am logged into.
-bash: debsums: command not found
 
@bbgeek17 same problem after reinstalling pvemanager packages.

Is there a way to downgrade to a previous minor version ? (pvemanager I mean, at least to confirm if changes in it's code created this)
 
Last edited:
bbgeek17 said:
Downgrading is not supported, or recommended. It's a manual task that is quiet advanced, and can completely break your system.
Is this a business production environment?

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Click to expand...
I would say half way. Part of the nodes are already in production, the other part are testing and migration to put into production.
Also, some of us are constrained by the legacy workstations available. FirefoX ESR115, though old, still actively has security updates.
 
Last edited:
Try to find a workstation with a different browser. Try incognito mode. Create a VM via CLI, install a more modern browser and try from there.

andreisrr said:
) Haven't tried yet the command line. So far it seems a browser related problem with JS and I pursued the matter as such.
Click to expand...
You mentioned in your original post that you have been changing permissions. That may be a red herring, but creating a VM from the CLI would at least confirm whether permissions are related to the issue.

The bottom line is that hundreds of thousands of people use Proxmox VE daily, and I have not seen a report similar to yours. This makes it more likely that the issue is specific to your environment.

You also mentioned a policy-restricted browser. Short of reproducing your exact environment, there is not much that can be suggested beyond temporarily working around those restrictions to confirm baseline functionality.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
- permissions are not a factor. Indeed I was working on a more granular set of permissions for some users and groups, however the permissions for the root user have not been affected in any way. The problem through the GUI affects both root user and the users being tested in a separate private window.
- my browser version is restricted by the rather old workstation it runs on, as it cannot be updated further. There are no restrictions regarding it's functionality and there are no adblocking and similar extensions enabled.
It is an unfortunate conundrum, as at the same time I am restricted by the GUI of other infrastructure equipment which ... won't run on newer OS.
- I am trying to get a temporary later browser on some computer connected to the admin VLAN.
- it seems to me as a small detail in the implementation of the "Create VM" wizard. And only there. I don't get JS errors anywhere else in the UI.
- such changes that affect viable browser I would have expected to be more widespread over the UI functions and come with a more significant PVEMANAGER version change then a minor revision... :-(
- CLI creation of VM works fine.
- at this time we are even seriously considering reinstalling PVE9 at an earlier minor version from existing ISO and capping updates for a while. At least until our beloved traesury releases some funds for upgrades for the little people :-(
 
Last edited:
As a temporary test/fix, given you can create VMs, build a Linux desktop one and try from there, if you can.

Install debsums and run it (apt install debsums), man debsums.
Depending on the result of the debsums run, you may still want to reinstall the UI kit:
apt install --reinstall pve-manager proxmox-widget-toolkit libjs-extjs

You can create a VM via cli: qm create 100
Then continue managing it via UI. You can also install nested PVE versioned earlier 9 , or even 8.

Has this ever worked for you? If I were in your shoes, I'd be trying to exclude odd-ball variables, i.e. browser.

Good luck

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
I have already reinstalled the GUI kit (at current version). And restarted the host.
Never tried nested virtualization (either pve or other).
I'll try a Vm as you said .would be interesting to see how I can get to manage the UI from it.
 
andreisrr said:
I'll try a Vm as you said .would be interesting to see how I can get to manage the UI from it.
Click to expand...
You can perform this directly from the console or via VNC.

From what you’ve described, you are following all the correct steps. No one else has reported a similar issue. Since your environment has not yet been fully excluded and there’s no reproducible case, you are the only one who can drive this to a resolution.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
You must log in or register to reply here.
Top Bottom
Back