[SOLVED] Since last update: Empty "Confirm" when creating vm

G

GeirO

Renowned Member
Jun 26, 2015
5
0
66
Hobro, Denmark
Hi all,

I've been running Proxmox since v3.4 on my server, and everything has worked as expected up until now.
I'm using the pve-test repository, and running a couple of vm's on lvm (whs2011 and Debian 8.1)

A couple of days ago I updated the host after the vm's where stopped with apt-get update & apt-get upgrade & apt-get dist-upgrade, rebooted the host, and started the two vm's without apparent errors.

Problem: When I try to create a new vm, the last page on the creation-tabs is empty (the "Confirm" tab), and the the only visible buttons ar "Back" and "Next". The "Next" button does not do anything, so I don't have the "Finish" button....

The task-window does not indicate a creation of vm (as expected, since the "Finish" button is not visible or pressed), nor do the sys-log show new entries.

The last time a new vm was made I was on proxmox-ve 4.1.30 (most probably), and since the last update I'm on 4.2.36

pve version before the last update (when I last created a vm withot error):
Code: 
root@Proxmox:~# pveversion -v
proxmox-ve: 4.1-30 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-4 (running version: 4.1-4/ccba54b0)
pve-kernel-4.2.6-1-pve: 4.2.6-30
pve-kernel-3.19.8-1-pve: 3.19.8-3
pve-kernel-4.1.3-1-pve: 4.1.3-7
pve-kernel-4.2.0-1-pve: 4.2.0-13
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 0.17.2-1
pve-cluster: 4.0-30
qemu-server: 4.0-43
pve-firmware: 1.1-7
libpve-common-perl: 4.0-42
libpve-access-control: 4.0-10
libpve-storage-perl: 4.0-38
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.4-18
pve-container: 1.0-36
pve-firewall: 2.0-14
pve-ha-manager: 1.0-16
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-5
lxcfs: 0.13-pve2
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve6~jessie

Updated pve-version as of now:
Code: 
root@Proxmox:~# pveversion -v
proxmox-ve: 4.1-36 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-8 (running version: 4.1-8/5df17429)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-3.19.8-1-pve: 3.19.8-3
pve-kernel-4.1.3-1-pve: 4.1.3-7
pve-kernel-4.2.0-1-pve: 4.2.0-13
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-31
qemu-server: 4.0-51
pve-firmware: 1.1-7
libpve-common-perl: 4.0-46
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-40
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-3
pve-container: 1.0-41
pve-firewall: 2.0-16
pve-ha-manager: 1.0-20
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-6
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie
root@Proxmox:~#

I'm at a loss where to start searching.

Hints, anyone?

Best Regards,
GeirO
 
based on your package list, you run the beta repository (pvetest).

if yes, I can confirm the issue.
 
tom said:
based on your package list, you run the beta repository (pvetest).

if yes, I can confirm the issue.
Click to expand...


I too run PVETEST and have exact same issue( blank Confirm screen in Create VM "wizard"). I would like to also add that I cannot edit "processors" of an existing VM either, through web GUI. It works through SSH and manual edit VM.conf file in CLI. However,I can edit Memory, CD/DVD Drive, just not the "processors" in the web GUI.

A temporary workaround I did was clone an existing VM and add/edit CD/dvd OS ISO to drive and reformat/install new OS. Edit what I could in GUI and edit rest in VMID.conf file. If it is your very first VM, maybe manually create one in CLI, but I don't know how, off of the top of my head as I am still a KVM/proxmox noob.

Thanks.
 
As I said, I'm running the pve-test repository. I'm thinking of changing back to the no-subscription repo, but that is another story.

It's not a problem waiting for this to be fixed, since this was just an extra vm I wanted to test with.
 
We found the problem, thanks for reporting.
 
we just uploaded the fixes to pvetest repo, please update and test again (works for me).
 
Sorry to report, the issue is not solved.

pveversion after a new update (pve-manager and pve-qemu-kvm was updated):
Code: 
root@Proxmox:~# pveversion -v
proxmox-ve: 4.1-36 (running kernel: 4.2.6-1-pve)
pve-manager: 4.1-9 (running version: 4.1-9/84a1a2e0)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-3.19.8-1-pve: 3.19.8-3
pve-kernel-4.1.3-1-pve: 4.1.3-7
pve-kernel-4.2.0-1-pve: 4.2.0-13
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-31
qemu-server: 4.0-51
pve-firmware: 1.1-7
libpve-common-perl: 4.0-46
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-40
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-4
pve-container: 1.0-41
pve-firewall: 2.0-16
pve-ha-manager: 1.0-20
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-6
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1
zfsutils: 0.6.5-pve7~jessie

I rebooted the host just to be sure, still not working.
 
Reporting success!

I did a normal apt-get update & apt-get upgrade this afternoon, and the pve-manager and qemu-server where updated.

Now the wizard shows the previous information in the summary, and a new vm could be made.
 
You must log in or register to reply here.
Top Bottom