[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15568810#comment-15568810
 ] 

ASF GitHub Bot commented on CLOUDSTACK-9280:
--------------------------------------------

GitHub user ProjectMoon reopened a pull request:

    https://github.com/apache/cloudstack/pull/1559

    CLOUDSTACK-9280: System VM volumes can be expunged if no SSVM exists.

    This commit adds a special SSVM endpoint which simply returns true for
    all operations sent to it, without actually doing anything. This
    allows for destroyed volumes of system VMs to be expunged when there
    are no hosts (and thus no system VMs) remaining to handle the volume
    destruction.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/greenqloud/cloudstack 
pr-volume-expunge-fix-master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1559.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1559
    
----
commit e1bc3a61933f4fd5a61b802b62ea19db5234dcbd
Author: jeff <j...@greenqloud.com>
Date:   2016-02-08T16:30:03Z

    CLOUDSTACK-9280: System VM volumes can be expunged if no SSVM exists.
    
    This commit adds a special SSVM endpoint which simply returns true for
    all operations sent to it, without actually doing anything. This
    allows for destroyed volumes of system VMs to be expunged when there
    are no hosts (and thus no system VMs) remaining to handle the volume
    destruction.

commit efe687548bdf5d8ab8dac37a36e34c4fe655dc88
Author: jeff <j...@greenqloud.com>
Date:   2016-10-07T15:39:12Z

    More fixes to allow volume expunging when primary storage is missing.
    
    The volume expunger is able to handle volumes which have no primary
    storage specified, but when loading these volumes, it is possible that
    a volume is missing the primary storage already which can cause an
    exception to be thrown. This commit changes this behavior so that when
    loading a volume to be expunged, not being able to find a primary data
    store is considered a warning rather than an exception.

----


> System VM volumes cannot be deleted when there are no system VMs
> ----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9280
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9280
>             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
(v6.3.4#6332)

Reply via email to