Volumes not destroyed after VM expunging
- Linguagem predominante
- Java
- Estrelas
- 3.1k
- Forks
- 1.4k
- Merge médio
- 6d 19h
- PRs com merge (30d)
- 32
Descrição
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
core
~~~
##### CLOUDSTACK VERSION
~~~
4.19.0.1
~~~
##### CONFIGURATION
##### OS / ENVIRONMENT
KVM hosts (both Ubuntu 22 and OL8 as OS) with NFS v4 primary storage
Using library: libvirt 8.0.0
Using API: QEMU 8.0.0
Running hypervisor: QEMU 6.2.0
##### SUMMARY
Some volumes (only ROOT volumes) remains in Destroy state after the related VM is correctly expunged. Trying to manually delete them results in the following error: "cannot unlock file 'path-to-the-qcow2': Permission denied. Libvirtd run as root on the hosts and I found no permission/ownership issues on the qcow2 disks.
##### STEPS TO REPRODUCE
~~~
I'm not really sure on how to reproduce the issue, seems related only to root disks in our environnement, as data disks give no issues if I try to delete them.
~~~
##### EXPECTED RESULTS
~~~
When the VM is expunged also the root disk is deleted as well
~~~
##### ACTUAL RESULTS
~~~
The root disk remain in the UI in "Destroy" state
~~~
Guia de contribuição
Direção de pesquisa
A issue não indica nenhum arquivo-fonte, teste ou ponto de entrada. Comece rastreando a limpeza dos volumes core durante a exclusão das VM no ambiente KVM/NFS relatado e investigue por que os volumes raiz permanecem no estado Destroy; considera-se concluído quando o volume raiz é removido junto com a VM excluída sem o erro de permissão relatado.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- java
- Domínio
- cloud, infrastructure
- Tipo de issue
- Bug
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 25/100