justinestruch commented on PR #6581:
URL: https://github.com/apache/cloudstack/pull/6581#issuecomment-3215486176
Hi all. I'm not sure if I should post here or open a separate issue. But I
am experiencing the same issue described that this PR should have fixed. I can
open a separate issue if needed. Thanks!
**Environment**
**Hypervisor**: VMware ESXI 8.0.3, Build 24674464
**Vcenter**: 8.0.3 Build 24022515
**Cloudstack**: 4.20.1.0
**Veeam**: 12.3.2.3617
**Issue**: When attempting to attach a volume to an instance that already
has backups. This fails with an error "Unable to attach volume to VM
i-8-172-VM/4b7302bf-3db7-4cab-8cba-448da64da59a, please specify a VM that does
not have any backups".
I have the global setting backup.enable.attach.detach.of.volume enabled.
**Steps to reproduce**
1. Create a new instance
2. Assign the instance to a backup offering
3. Start a backup and wait for it to complete
4. Create and add a new volume to the instance
5. NOTE: Attaching an exiting volume will cause the same error
Here's some relevant logs from
/var/log/cloudstack/management/management-server.log if these help
`2025-08-22 15:18:22,018 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(qtp1404565079-21:[ctx-c51d6d8c, ctx-f7bc6659]) (logid:0ca85635) submit async
job-1383, details: AsyncJob
{"accountId":2,"cmd":"org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin","cmdInfo":"{\"virtualmachineid\":\"2449395c-ee41-4c44-8240-f1243ee15403\",\"response\":\"json\",\"ctxUserId\":\"2\",\"sessionkey\":\"GUhq1rHYTujptXFAIfhoHYjAJBA\",\"httpmethod\":\"GET\",\"ctxStartEventId\":\"3645\",\"id\":\"4fbab46d-eae3-4246-b596-11ce15387399\",\"ctxDetails\":\"{\\\"interface
com.cloud.storage.Volume\\\":\\\"4fbab46d-eae3-4246-b596-11ce15387399\\\",\\\"interface
com.cloud.vm.VirtualMachine\\\":\\\"2449395c-ee41-4c44-8240-f1243ee15403\\\"}\",\"ctxAccountId\":\"2\",\"uuid\":\"4fbab46d-eae3-4246-b596-11ce15387399\",\"cmdEventType\":\"VOLUME.ATTACH\"}","cmdVersion":0,"completeMsid":null,"created":null,"id":1383,"initMsid":345049081830,"instanceId":155,"instanceType":"Volume","lastPolled":null,"lastUpdated":n
ull,"processStatus":0,"removed":null,"result":null,"resultCode":0,"status":"IN_PROGRESS","userId":2,"uuid":"290945f4-2218-4f20-b12d-2b456635e769"}
2025-08-22 15:18:22,018 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl$5]
(API-Job-Executor-7:[ctx-fe7f2061, job-1383]) (logid:290945f4) Executing
AsyncJob
{"accountId":2,"cmd":"org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin","cmdInfo":"{\"virtualmachineid\":\"2449395c-ee41-4c44-8240-f1243ee15403\",\"response\":\"json\",\"ctxUserId\":\"2\",\"sessionkey\":\"GUhq1rHYTujptXFAIfhoHYjAJBA\",\"httpmethod\":\"GET\",\"ctxStartEventId\":\"3645\",\"id\":\"4fbab46d-eae3-4246-b596-11ce15387399\",\"ctxDetails\":\"{\\\"interface
com.cloud.storage.Volume\\\":\\\"4fbab46d-eae3-4246-b596-11ce15387399\\\",\\\"interface
com.cloud.vm.VirtualMachine\\\":\\\"2449395c-ee41-4c44-8240-f1243ee15403\\\"}\",\"ctxAccountId\":\"2\",\"uuid\":\"4fbab46d-eae3-4246-b596-11ce15387399\",\"cmdEventType\":\"VOLUME.ATTACH\"}","cmdVersion":0,"completeMsid":null,"created":null,"id":1383,"initMsid":345049081830,"instanceId":155,"instanceType":"Volume","lastPolled":null,"lastUpdated":null,"processStatus":0,"
removed":null,"result":null,"resultCode":0,"status":"IN_PROGRESS","userId":2,"uuid":"290945f4-2218-4f20-b12d-2b456635e769"}
2025-08-22 15:18:22,034 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-7:[ctx-fe7f2061, job-1383]) (logid:290945f4) Complete async
job-1383, jobStatus: FAILED, resultCode: 431, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"431","errortext":"Unable
to attach volume to VM i-8-171-VM/2449395c-ee41-4c44-8240-f1243ee15403, please
specify a VM that does not have any backups"}
2025-08-22 15:18:22,041 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl$5]
(API-Job-Executor-7:[ctx-fe7f2061, job-1383]) (logid:290945f4) Done executing
org.apache.cloudstack.api.command.admin.volume.AttachVolumeCmdByAdmin for
job-1383`
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
