cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Hair (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9280) System VM volumes cannot be deleted when there are no system VMs
Date Fri, 05 Feb 2016 16:03:39 GMT


Jeff Hair commented on CLOUDSTACK-9280:

This was discovered when trying to clean up zones completely. This problem goes all the way
back to at least 4.2 it seems. In the case of 4.6+, the zone deletion will fail because it
detects volumes still existing in the database. Removing the volumes in the database allows
the zone to be deleted.

We will file a pull request with a possible solution to this issue. I will likely implement
some special "endpoint" that is only used in this specific case. Any other suggestions are
most welcome.

> System VM volumes cannot be deleted when there are no system VMs
> ----------------------------------------------------------------
>                 Key: CLOUDSTACK-9280
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.6.0, 4.7.0
>            Reporter: Jeff Hair
> Scenario: When deleting a zone, everything under it must be removed. This results in
the system VMs being destroyed as there are no more hosts running.
> The storage cleanup thread properly detects that there are volumes to be deleted, but
it cannot delete them because the endpoint selection fails with "No remote endpoint to send
DeleteCommand, check if host or ssvm is down?"

This message was sent by Atlassian JIRA

View raw message