Error Detaching Volume on GlusterFS Primary Storage
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
Primary Storage (GlusterFS)
~~~
##### CLOUDSTACK VERSION
~~~
4.17.1.0
~~~
##### CONFIGURATION
##### OS / ENVIRONMENT
~~~
CentOS Linux 7 (Core)
qemu-img version 2.12.0
glusterfs 6.1
~~~
##### SUMMARY
Can't detach volumes created on GlusterFS primary storage from VM. Tested on two different cloudstack installations. Everything works fine with other primary storage types. The volume can be detached and removed if the VM status is stopped but not when running.
##### STEPS TO REPRODUCE
~~~
- Create GlusterFS Primary Storage with tag
- Create Disk Offering that uses just crated GlusterFS Primary Storage's tag.
- Create Volume using just created Disk Offering
- Attach Volume to VM
- Detach Volume from VM
~~~
##### EXPECTED RESULTS
~~~
- Success detaching Volume
~~~
##### ACTUAL RESULTS
~~~
- (test-detach) Failed to detach volume test-detach from VM test-vm-for-gluster ; com.cloud.exception.InternalErrorException: disk: /mnt/b440b605-a876-35f8-be84-2b5696650654/5605035d-e060-42a6-89a1-6f9c949463fc is not attached before
~~~
Contributor guide
Research direction
Start by reproducing the detach flow described in the issue with GlusterFS primary storage on a running VM, using the listed CentOS, qemu-img, and glusterfs environment. Trace the source of the “is not attached before” error and compare it with other primary-storage types. Done means the volume detaches successfully while the VM is running and the reported scenario is covered by regression testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- centos
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100