[ https://issues.apache.org/jira/browse/CLOUDSTACK-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14162556#comment-14162556 ]
ASF subversion and git services commented on CLOUDSTACK-4987: ------------------------------------------------------------- Commit 794ee6929d078fd919842f2c1f55156f133d7934 in cloudstack's branch refs/heads/master from [~jessicawang] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=794ee69 ] CLOUDSTACK-4987: UI > Instances > detailView > NICs tab > Add network to VM > Network dropdown => (1) For root-admin, populate networks of all accounts. (2) For regular-user/domain-admin, populate only networks belonging to this VM owner. > 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: Jessica Wang > Fix For: 4.4.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.3.4#6332)