[
https://issues.apache.org/jira/browse/CLOUDSTACK-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13693093#comment-13693093
]
ASF subversion and git services commented on CLOUDSTACK-3155:
-------------------------------------------------------------
Commit 34bdd1e1b3e94d7afff3f9a5b865065a5157158f in branch
refs/heads/master-6-17-stable from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=34bdd1e ]
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 <sate...@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
