You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/09/16 17:35:34 UTC
[jira] [Commented] (CLOUDSTACK-7546) [LXC] agent addition to MS is
failing if we stop service NetworkManager
[ https://issues.apache.org/jira/browse/CLOUDSTACK-7546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135603#comment-14135603 ]
ASF subversion and git services commented on CLOUDSTACK-7546:
-------------------------------------------------------------
Commit 75d01971e8d5f27f65ba0b98fc6d9aba057757e7 in cloudstack's branch refs/heads/master from [~kishan]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=75d0197 ]
CLOUDSTACK-7546: cloudstack-setup-agent considers distro as RHEL5 if no conditions match. Add check to identify RHEL7 distro and consider it as RHEL6. If there is anything specific required for RHEL7, it can be added later
> [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.<init>(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)