You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/24 14:12:20 UTC

[jira] [Commented] (CLOUDSTACK-3155) [VMware] Deletion of zone should not be allowed if VMware DC is still associated with that zone.

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

ASF subversion and git services commented on CLOUDSTACK-3155:
-------------------------------------------------------------

Commit e9df9c29bde4374e443c91ed91e2706b6074082f in branch refs/heads/master from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=e9df9c2 ]

CLOUDSTACK-3155 [VMware] Deletion of zone should not be allowed if VMware DC is still associated with that zone.

Check if there exists any VMware DC already associated with this zone. Deny zone deletion if true.

Signed-off-by: Sateesh Chodapuneedi <sa...@apache.org>

                
> [VMware] Deletion of zone should not be allowed if VMware DC is still associated with that zone.
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3155
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3155
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>              Labels: vmware
>
> Deletion of zone should not be allowed if VMware DC is still associated with that zone.
> Let user go back and remove VMware DC from cloudstack zone and re-try deletion of zone.
> This is inline with the way deletion of zone is handled if there are pods/physical networks etc. that are part of zone already.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira