[
https://issues.apache.org/jira/browse/CLOUDSTACK-4751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048617#comment-14048617
]
Namita Chaudhari commented on CLOUDSTACK-4751:
----------------------------------------------
I am working on this bug and had a query regarding it.
If a network is already configured on VM, then why do we have to add same
network again to the VM? Is there any specific purpose behind doing so? Can
anyone please help me in this?
> Can't add a single network multiple times to a VM
> -------------------------------------------------
>
> Key: CLOUDSTACK-4751
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4751
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.2.0
> Reporter: John Beredimas
> Assignee: Namita Chaudhari
>
> Trying to add a network multiple times to a single VM fails with release 4.2.
> This worked OK with release 4.1.
> This should be fairly easy to reproduce. Here is my cloudmonkey output:
> cloudmonkey> add nictovirtualmachine
> virtualmachineid=a8d35e16-cb65-46c5-aa8d-d07e533326ee
> networkid=5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5
> Async job 115feb72-0abf-4cea-8e67-8d61d768e51e failed
> Error 530, A NIC already exists for VM:i-34-1015-VM in network:
> 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5
> accountid = 2e64c73f-a173-419a-8dc8-6739aa4e4f9d
> cmd = org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> created = 2013-09-27T15:44:21+0300
> jobid = 115feb72-0abf-4cea-8e67-8d61d768e51e
> jobprocstatus = 0
> jobresult:
> errorcode = 530
> errortext = A NIC already exists for VM:i-34-1015-VM in network:
> 5f575638-5e53-4b74-9ec6-5b8e3fa8a4f5
> jobresultcode = 530
> jobresulttype = object
> jobstatus = 2
> userid = 59322c02-abf9-4be2-a7c5-a67947a257fb
--
This message was sent by Atlassian JIRA
(v6.2#6252)
