Unable to delete linked VM

Kevin Meijer

Active Member
Apr 25, 2018
12
0
41
32
I seem to have gotten myself in a situation in where I am unable to delete my VMs.

I am using a single Proxmox node with an external Ceph cluster, I've got a dedicated PVE pool (rdb_pve) on which I am running a couple of VMs.
Each of those VMs are cloned from 1 of 2 templates using a linked clone, the clone goes fine (Instant) and I can start and use the VM just fine. However, when attempting to delete one of these linked VMs the task will fail, the image will get removed from Ceph but it seems Proxmox is attempting to delete it again at which it fails.
Another symptom is that I am unable to view the contents of the Ceph storage, it returns the error rbd error: rbd: listing images failed: (2) No such file or directory (500).

The only way to remove a VM is by deleting its /etc/pve/qemu-server/*.conf file.
Does anyone know what this is and how to fix this?
 

Attachments

  • task.log
    task.log
    5 KB · Views: 2
  • Screenshot 2020-07-02 at 13.50.05.png
    Screenshot 2020-07-02 at 13.50.05.png
    95.5 KB · Views: 4
hi,

in your log file:
Code:
2020-07-02 13:42:50.673 7f9b05031f40 -1 Errors while parsing config file!
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 Errors while parsing config file!
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
did not load config file, using default settings.
2020-07-02 13:42:50.781 7f665506df40 -1 Errors while parsing config file!
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 Errors while parsing config file!
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory

so it seems /etc/ceph/ceph.conf can't be found?
 
hi,

in your log file:
Code:
2020-07-02 13:42:50.673 7f9b05031f40 -1 Errors while parsing config file!
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 Errors while parsing config file!
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.673 7f9b05031f40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
did not load config file, using default settings.
2020-07-02 13:42:50.781 7f665506df40 -1 Errors while parsing config file!
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 Errors while parsing config file!
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /etc/ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open /.ceph/ceph.conf: (2) No such file or directory
2020-07-02 13:42:50.781 7f665506df40 -1 parse_file: cannot open ceph.conf: (2) No such file or directory

so it seems /etc/ceph/ceph.conf can't be found?
I saw that too yea, but i am unsure if it is relevant since I am using an external cluster, the keyring is already in /etc/pve/priv/ceph/ceph.keyring
I am not even sure of what to put in there in this situation
 
I just created a ceph.conf with the monitors in there, but it doesn't seem to fix this issue. I am still getting TASK ERROR: rbd error: rbd: listing images failed: (2) No such file or directory.

The error also seems to me like it is attempting to list images in a pool called rbd, but that is not the name of my pool. Does anyone know where to look?
 
I finally found a solution to this issue, it wasn't Proxmox's fault but it was a Ceph issue.

For some reason every-time someone attempted to list the RBD images (For example, using rbd ls <pool_name>) an error message was shown (rbd: listing images failed: (2) No such file or directory).
The solution was to delete the specified image (Since it was corrupted anyway).

After that everything worked just fine.
 

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!