When I add a host to a cluster/pod/zone in 4.4 I get
2014-05-13 08:51:27,073 DEBUG [c.c.u.s.SSHCmdHelper]
(DirectAgent-20:ctx-bf9610f7) Executing cmd: mkdir -p /opt/cloud/bin
/var/log/cloud
2014-05-13 08:51:28,089 DEBUG [c.c.u.s.SSHCmdHelper]
(DirectAgent-20:ctx-bf9610f7) Ssh executed failed
java.lang.NullPointerException
at
com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShotWithExitCode(SSHCmdHelper.java:159)
at
com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmdOneShot(SSHCmdHelper.java:170)
at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmd(SSHCmdHelper.java:66)
at com.cloud.utils.ssh.SSHCmdHelper.sshExecuteCmd(SSHCmdHelper.java:91)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.setupServer(CitrixResourceBase.java:4845)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:4674)
at
com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:490)
at
com.cloud.hypervisor.xen.resource.XcpOssResource.executeRequest(XcpOssResource.java:176)
at
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:216)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:49)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:56)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:103)
at
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:53)
at
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:46)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
The dir does exist on the host so mkdir -p does not return an error.
This happens on the 4.3 version of devcloud2 on macosx and on a
xenserver 6.0.2 host with a windows ms.
Anybody else saw this?
--
Daan
