Hi Dann,
The only way we could resolve this was by deleting the VM, after that the error
went away. Fortunately the VM wasn’t important but we couldn’t do that
normally.
I tried looking in the vm table but couldn’t see anything with the status of
starting so it may have been in another table but no idea which one.
Thanks
Ian
-----Original Message-----
From: Daan <[email protected]>
Sent: 01 December 2025 09:29
To: [email protected]
Subject: Re: Storage maintenance error
Ian,
Did you investigate the VM with internal ids 40/41? Do any of those still exist?
Note that "id":41,"instanceName":"i-4-40-VM”, is kind of a contradiction. I
would expect the name to reflect the internal id (“i-“ + account-id + “-“ +
internal-vm-id + “-VM” by default). No idea if this is the root cause or how
this came to be, but I would look in this direction first.
On 2025/11/26 16:25:35 Ian Tobin wrote:
> Hi,
>
> We have a continuing issue where we place storage into maintenance then cant
> cancel maintenance using the GUI.
>
> When we select cancel maintenance on the storage, the error is
>
> com.cloud.exception.InsufficientServerCapacityException: Unable to create a
> deployment for VM instance
> {"id":41,"instanceName":"i-4-40-VM","state":"Starting","type":"User","uuid":"21a4bb1c-81d0-49d7-ae6d-72f70e643c30"}Scope=interface
> com.cloud.dc.DataCenter; id=1
>
> It appears a past issue is stuck in the database and causing the validations
> check to fail.
>
> The work around at the moment is to login to mysql and issue
>
> update storage_pool set status='Up' where id=3;
>
> How can we remove the previous error to stop this happening?
>
> Thanks
>
> Ian
>
>
>
>
