Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8529AC454 for ; Fri, 19 Jul 2013 14:54:49 +0000 (UTC) Received: (qmail 53767 invoked by uid 500); 19 Jul 2013 14:54:49 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 53749 invoked by uid 500); 19 Jul 2013 14:54:49 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 53741 invoked by uid 500); 19 Jul 2013 14:54:49 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 53738 invoked by uid 99); 19 Jul 2013 14:54:49 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 19 Jul 2013 14:54:49 +0000 Date: Fri, 19 Jul 2013 14:54:49 +0000 (UTC) From: "Rayees Namathponnan (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Closed] (CLOUDSTACK-2546) [Automation] Failed to add second NIC to vm in KVM environment MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rayees Namathponnan closed CLOUDSTACK-2546. ------------------------------------------- This test case is working now > [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 > Assignee: Mice Xia > 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