Hi Ricardo, It looks like the async job got cancelled by the cancellation timeout set there. Volume state should ideally change to ready once the job is cancelled. You could check at the hypervisor if any migration task is still going on.
-Jithin From: Ricardo Pertuz <[email protected]> Date: Monday, 24 April 2023 at 8:29 PM To: [email protected] <[email protected]> Subject: Error migrating volume ACS 4.15.2.0 Hi, I’m trying to migrate some root volumes to another primary storage, and I got the following error: jobStatus: FAILED, resultCode: 530, result: org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Unable to serialize: Job is cancelled as it has been blocking others for too long"} 2023-04-24 09:44:41,673 ERROR [c.c.a.ApiAsyncJobDispatcher] (API-Job-Executor-37:ctx-ebd3da18 job-62293) (logid:954fc36b) Unexpected exception while executing org.apache.cloudstack.api.command.admin.volume.MigrateVolumeCmdByAdmin com.cloud.utils.exception.CloudRuntimeException: Unable to serialize: Job is cancelled as it has been blocking others for too long Not sure if it only the query job that failed or my volumes got corrupted or something as they are still in migrating/creating state. Regards, Ricardo
