Delete VMS delete but Proxmox keeps it listed

C

Chris Rivera

Guest
I have gone thru the cluster lately trying to clean up all vms that are cancelled & terminated and found a new issue that has arrised.

While the delete option say ok as it has finished. the vm does not actually get removed from the left panel under the node its in or the right side which lists all vms and full details.

If i try to delete the vm again i get the following:


Warning: Unknown iptable module: xt_connlimit, skipped

Destroying container private area: /var/lib/vz/private/357
Warning: failed to remove /var/lib/vz/root/357: No such file or directory
Container private area was destroyed
TASK OK

########################


since it has been deleted... i cannot start the vm as i get the following error:

Warning: Unknown iptable module: xt_connlimit, skipped
Starting container ...
Container private area /var/lib/vz/private/445 does not exist
[FONT=tahoma, arial, verdana, sans-serif]TASK ERROR: command 'vzctl start 445' failed: exit code 43[/FONT]


[FONT=tahoma, arial, verdana, sans-serif]##########################[/FONT]

[FONT=tahoma, arial, verdana, sans-serif]so the vm is actually getting deleted but not being removed from the list.... this is a growing issue as we have over 30-60 vms that need to be deleted+ and only half of them are being removed.


is there a script we can run that will check proxmox if the vms exists... and if not then remove the vm from the list?


[/FONT]
 
Destroying container private area: /var/lib/vz/private/357
Warning: failed to remove /var/lib/vz/root/357: No such file or directory
Container private area was destroyed
TASK OK

########################


since it has been deleted... i cannot start the vm as i get the following error:

Warning: Unknown iptable module: xt_connlimit, skipped
Starting container ...
Container private area /var/lib/vz/private/445 does not exist
TASK ERROR: command 'vzctl start 445' failed: exit code 43

You removed 357, and now start 445 - those are different containers.
 
sorry for the mixup.... i have many of these that are the same



qm destroy 223
disk image '/var/lib/vz/images/223/vm-223-disk-1.raw' does not exists


root@Proxmox10:~# vzctl destroy 357
Warning: Unknown iptable module: xt_connlimit, skipped
stat(/var/lib/vz/root/357): No such file or directory
Container is currently mounted (umount first)
root@Proxmox10:~# umount /var/lib/vz/root/357
umount: /var/lib/vz/root/357: not found


root@proxmox8:~# vzctl destroy 502
stat(/var/lib/vz/root/502): No such file or directory
Container is currently mounted (umount first)
root@proxmox8:~# umount /var/lib/vz/root/502
umount: /var/lib/vz/root/502: not found


root@proxmox6:~# vzctl destroy 431
Warning: Unknown iptable module: xt_connlimit, skipped
stat(/var/lib/vz/root/431): No such file or directory
Container is currently mounted (umount first)
root@proxmox6:~# umount /var/lib/vz/root/431
umount: /var/lib/vz/root/431: not found


root@proxmox8:~# vzctl destroy 172
stat(/var/lib/vz/root/172): No such file or directory
Container is currently mounted (umount first)
root@proxmox8:~# umount /var/lib/vz/root/172
umount: /var/lib/vz/root/172: not found


root@proxmox8:~# vzctl destroy 328
stat(/var/lib/vz/root/328): No such file or directory
Container is currently mounted (umount first)
root@proxmox8:~# umount /var/lib/vz/root/328
umount: /var/lib/vz/root/328: not found


root@proxmox8:~# vzctl destroy 210
stat(/var/lib/vz/root/210): No such file or directory
Container is currently mounted (umount first)
root@proxmox8:~# umount /var/lib/vz/root/210
umount: /var/lib/vz/root/210: not found


root@Proxmox10:~# vzctl destroy 441
Warning: Unknown iptable module: xt_connlimit, skipped
stat(/var/lib/vz/root/441): No such file or directory
Container is currently mounted (umount first)
root@Proxmox10:~# umount /var/lib/vz/root/441
umount: /var/lib/vz/root/441: not found


root@Proxmox10:~# vzctl destroy 340
Warning: Unknown iptable module: xt_connlimit, skipped
stat(/var/lib/vz/root/340): No such file or directory
Container is currently mounted (umount first)
root@Proxmox10:~# umount /var/lib/vz/root/340
umount: /var/lib/vz/root/340: not found


root@Proxmox10:~# vzctl destroy 363
Warning: Unknown iptable module: xt_connlimit, skipped
stat(/var/lib/vz/root/363): No such file or directory
Container is currently mounted (umount first)
root@Proxmox10:~# umount /var/lib/vz/root/363
umount: /var/lib/vz/root/363: not found




Yet all these vms still show up in proxmox interface.

If i get vm ids from the command line (vzlist -HS -o ctid) i also get these ids back from vms that are physically not on the cluster.
 
Yes, the config files are in that location.

Currently the cluster is offline out of sync so i cannot remove the conf file. When the system becomes in quorum ill try to remove the file again.


Is their a process to verify this so this doesn't need to be done manually or if we can check for the vz files & conf file... if one of the other is missing to let the cloud administrator know so we can fix?
 
This does not happen all the time but i can say does happen from time to time.

Next time it happens i will be sure to track cluster health ( quorum ) to see if this is why it deleted the vm and not the config.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!