[
https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873645#comment-13873645
]
Alena Prokharchyk commented on CLOUDSTACK-4987:
-----------------------------------------------
Need to relax this check for Root admin - he should be able to deploy his own
vms in any CS network. As an example of the use case - Admin needs to deploy
some system vm in user's network that will provide some service for user vms,
but he doesn't wanna regular user see this vm.
> Able to add isolated network belonging to an account to a virtual machine
> belonging to different account
> --------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4987
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4987
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Devices
> Affects Versions: 4.2.0, 4.3.0
> Environment: Observed on KVM. Did not test on Xen and VMware yet.
> Reporter: Gaurav Aradhye
> Assignee: Wei Zhou
> Fix For: 4.2.1, 4.3.0
>
>
> 1. Deploy an instance in an account
> 2. Create an isolated network in different account
> 3. Add this isolated network to the VM (both belong to different accounts
> within same domain)
> As per the test plan - Test case no. 18
> (https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+networks+to+VM+Test+cases),
> API should fail in this case.
> But it has been observed that network gets added successfully and new NIC can
> be seen in VM's NICs list for this network.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
