cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kishan Kavala (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-7546) [LXC] agent addition to MS is failing if we stop service NetworkManager
Date Tue, 16 Sep 2014 15:36:34 GMT

     [ 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.<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)

Mime
View raw message