leo79901 opened a new issue, #12218:
URL: https://github.com/apache/cloudstack/issues/12218

   ### problem
   
   While I was trying to create an instance from a backup, it failed.
   
   I have tried both NFS and Linstor storage as target pools when restoring 
from an NFS backup, and encountered this error.
   
   `2025-12-10 09:17:21,196 ERROR [c.c.a.ApiAsyncJobDispatcher] 
(API-Job-Executor-53:[ctx-29561268, job-857]) (logid:0ad3bb95) Unexpected 
exception while executing 
org.apache.cloudstack.api.command.admin.vm.CreateVMFromBackupCmdByAdmin 
com.cloud.utils.exception.CloudRuntimeException: Failed to create Instance 
[i-2-65-VM] from backup 
[{"externalId":"i-2-64-VM\/2025.12.10.08.53.42","name":"nfs-0-nfs-0","uuid":"3acd3982-663f-4d2f-874c-364c5bb22a4a"}]
 due to: Unable to restore contents from the backup volume 
[0c3785e2-9473-4c5f-89d7-7c9e449e8bc7]..
   `
   
   I suspect that during the restoration process, the file name being looked 
for may not match the actual file name stored in the backup, which could be 
causing the failure to locate the backup file.
   
   Here is a summary of some information. I will try to upload the relevant 
logs for this part.
   
   
   <html xmlns:v="urn:schemas-microsoft-com:vml" 
xmlns:o="urn:schemas-microsoft-com:office:office" 
xmlns:x="urn:schemas-microsoft-com:office:excel" 
xmlns="http://www.w3.org/TR/REC-html40";>
   <head>
   
   <meta name=Generator content="Microsoft Excel">
   <!--[if !mso]>
   <style>
   v\:* {behavior:url(#default#VML);}
   o\:* {behavior:url(#default#VML);}
   x\:* {behavior:url(#default#VML);}
   .shape {behavior:url(#default#VML);}
   </style>
   <![endif]-->
   <style>
   <!--.font0
        {color:#000000;
        font-size:11.0pt;
        font-family:宋体;
        font-weight:400;
        font-style:normal;
        text-decoration:none;}
   .font1
        {color:#000000;
        font-size:10.5pt;
        font-family:Segoe UI;
        font-weight:400;
        font-style:normal;
        text-decoration:none;}
   br
        {mso-data-placement:same-cell;}
   td
        {padding-top:1px;
        padding-left:1px;
        padding-right:1px;
        mso-ignore:padding;
        color:#000000;
        font-size:11.0pt;
        font-weight:400;
        font-style:normal;
        text-decoration:none;
        font-family:宋体;
        mso-generic-font-family:auto;
        mso-font-charset:134;
        mso-number-format:General;
        border:none;
        mso-background-source:auto;
        mso-pattern:auto;
        text-align:general;
        vertical-align:middle;
        white-space:nowrap;
        mso-rotate:0;
        mso-protection:locked visible;}
   .et2
        {mso-generic-font-family:auto;
        mso-font-charset:134;
        border:.5pt solid #000000;}
   .et3
        {font-size:10.5pt;
        font-family:Segoe UI;
        mso-generic-font-family:auto;
        mso-font-charset:134;
        border:.5pt solid #000000;}
   -->
   </style>
   </head>
   <body>
   <!--StartFragment-->
   
   No. | Storage Type | Backup Stroage | Volume ID | Volume Name in backup | 
Backup info in database
   -- | -- | -- | -- | -- | --
   1 | Linstor | NFS | d9283f2c-26e9-4adf-9816-a54537b6e81a | 
root.drbd1039.qcow2 | 
[{"uuid":"d9283f2c-26e9-4adf-9816-a54537b6e81a","type":"ROOT","size":107374182400,"path":"d9283f2c-26e9-4adf-9816-a54537b6e81a","deviceId":0,"diskOfferingId":"5081ea5d-87ec-4903-a30d-7fab9c378ce8"}]
   2 | NFS | NFS | 0c3785e2-9473-4c5f-89d7-7c9e449e8bc7 | 
root.0c3785e2-9473-4c5f-89d7-7c9e449e8bc7.qcow2 | 
[{"uuid":"0c3785e2-9473-4c5f-89d7-7c9e449e8bc7","type":"ROOT","size":107374182400,"path":"0c3785e2-9473-4c5f-89d7-7c9e449e8bc7","deviceId":0,"diskOfferingId":"880ba876-defd-4bf3-b28b-1a973c9dff53"}]
   
   
   <!--EndFragment-->
   </body>
   
   </html>
   
   
   
   
   ### versions
   
   4.22.0
   
   ### The steps to reproduce the bug
   
   1. Provision virtual machines using LINSTOR and NFS as the primary storage 
types respectively.
   2. Back up the VMs to the NFS-based backup repository.
   3. Attempt to restore the backup to a new virtual machine → Restore fails.
   4. Shut down the original virtual machine, then restore the same backup to 
it → Restore succeeds.
   
   
   ### What to do about it?
   
   [log.txt](https://github.com/user-attachments/files/24066762/log.txt)


-- 
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]

Reply via email to