Re: [jira] [Commented] (CLOUDSTACK-2546) [Automation] Failed to add second NIC to vm in KVM environment

[Marcus Sorensen <sh...@gmail.com>]

No, the feature was to add new networks, remove old ones. Same network was
only ever allowed because it was possible also to have two NICs on one
network via deployVirtualMachine and we wanted to be consistent. I think it
has since been disallowed per the aforementioned patch, but apparently the
test wasn't changed.
On May 17, 2013 1:05 AM, "Prasanna Santhanam (JIRA)" <ji...@apache.org>
wrote:

>
>     [
> https://issues.apache.org/jira/browse/CLOUDSTACK-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13660420#comment-13660420]
>
> Prasanna Santhanam commented on CLOUDSTACK-2546:
> ------------------------------------------------
>
> I think the feature was to allow adding multiple nics on the same network.
>
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/Add+Remove+Networks+to+VMs
>
> Should this be brought up on the list? Marcus and the folks at
> betterservers added this test as written.
>
> > [Automation] Failed to add second NIC to vm in KVM environment
> > ---------------------------------------------------------------
> >
> >                 Key: CLOUDSTACK-2546
> >                 URL:
> https://issues.apache.org/jira/browse/CLOUDSTACK-2546
> >             Project: CloudStack
> >          Issue Type: Bug
> >      Security Level: Public(Anyone can view this level - this is the
> default.)
> >          Components: Network Controller
> >    Affects Versions: 4.2.0
> >         Environment: KVM
> > Build : Latest master build
> >            Reporter: Rayees Namathponnan
> >            Priority: Blocker
> >             Fix For: 4.2.0
> >
> >
> > Automation test case /test/integration/smoke/test_nic.py failed
> > Steps to reproduce
> > 1) Create and account, service offering
> > 2) Create Network offering (isolated) and Create network
> > 3) Create VM with the network
> > 4) After VM is up, add another network to VM
> > Expected result
> > Second nic should be added
> > Actual result
> > Failed to add second nic
> > 2013-05-16 10:49:07,804 ERROR [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-68:job-292) Unexpected exception while executing
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd
> > com.cloud.utils.exception.CloudRuntimeException: A NIC already exists
> for VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030
> >         at
> com.cloud.vm.UserVmManagerImpl.addNicToVirtualMachine(UserVmManagerImpl.java:844)
> >         at
> org.apache.cloudstack.api.command.user.vm.AddNicToVMCmd.execute(AddNicToVMCmd.java:109)
> >         at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155)
> >         at
> com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437)
> >         at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> >         at
> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> >         at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> >         at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> >         at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> >         at java.lang.Thread.run(Thread.java:679)
> > 2013-05-16 10:49:07,809 DEBUG [cloud.async.AsyncJobManagerImpl]
> (Job-Executor-68:job-292) Complete async job-292, jobStatus: 2, resultCode:
> 530, result: Error Code: 530 Error text: A NIC already exists for
> VM:i-36-74-VM in network: 632e241e-4071-445b-a2a8-d83606ae8030
> > 2013-05-16 10:49:09,334 DEBUG
> [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Zone 1
> is ready
>
> --
> 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
>