You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2014/01/16 18:56:21 UTC
[jira] [Reopened] (CLOUDSTACK-4987) Able to add isolated network
belonging to an account to a virtual machine belonging to different account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alena Prokharchyk reopened CLOUDSTACK-4987:
-------------------------------------------
Assignee: Alena Prokharchyk (was: Wei Zhou)
> 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: Alena Prokharchyk
> 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)