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 929BC112F2 for ; Tue, 16 Sep 2014 15:36:34 +0000 (UTC) Received: (qmail 18352 invoked by uid 500); 16 Sep 2014 15:36:34 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 18327 invoked by uid 500); 16 Sep 2014 15:36:34 -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 18318 invoked by uid 500); 16 Sep 2014 15:36:34 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 18315 invoked by uid 99); 16 Sep 2014 15:36:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Sep 2014 15:36:34 +0000 Date: Tue, 16 Sep 2014 15:36:34 +0000 (UTC) From: "Kishan Kavala (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (CLOUDSTACK-7546) [LXC] agent addition to MS is failing if we stop service NetworkManager 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-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kishan Kavala resolved CLOUDSTACK-7546. --------------------------------------- Resolution: Fixed > [LXC] agent addition to MS is failing if we stop service NetworkManager > ------------------------------------------------------------------------ > > Key: CLOUDSTACK-7546 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7546 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: KVM > Affects Versions: 4.5.0 > Reporter: shweta agarwal > Assignee: Kishan Kavala > Priority: Blocker > Fix For: 4.5.0 > > > Repro Steps: > 1. Install MS and agent on two different host > 2. Stop networkmanager on host and also chkconfig networkmanager off > 3. Create a Advance zone with LXC > Bug: > Agent addition to CS will fail > agent log shows : > 2014-09-15 16:38:26,027 ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: > com.cloud.utils.exception.CloudRuntimeException: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory > at com.cloud.hypervisor.kvm.resource.LibvirtComputingResource.configure(LibvirtComputingResource.java:830) > at com.cloud.agent.Agent.(Agent.java:163) > at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:401) > at com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:371) > at com.cloud.agent.AgentShell.launchAgent(AgentShell.java:355) > at com.cloud.agent.AgentShell.start(AgentShell.java:465) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.commons.daemon.support.DaemonLoader.start(DaemonLoader.java:243) > 2014-09-15 16:39:37,406 INFO [cloud.agent.AgentShell] (main:null) Agent started > Additional info : > checked Libvirtd status once agent fails to start and status was stopped in above scenario > But if we dont stop networkmanager service before adding agent to CS then agent addition succeeds without fail. -- This message was sent by Atlassian JIRA (v6.3.4#6332)