Samuel created CLOUDSTACK-8358:
----------------------------------

             Summary: Cloudstack 4.4.2 Error adding devcloud host IOException 
scp error: Invalid location of vmops in patch file
                 Key: CLOUDSTACK-8358
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8358
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: DevCloud, Management Server, marvin, XCP, XenServer
    Affects Versions: 4.3.2, 4.4.2
         Environment: Ubuntu 14.04, x86_64, devcloud2, xen 4.1
            Reporter: Samuel


I am trying to deploy the devcloud2 data centre but I noticed a lot of the 
errors I was getting were because of the missing scripts in the patch file. I 
have tried to point the locations in the patch script to the correct locations 
and they all seem to work except the file url for vmops.

See error log below:

r.CitrixResourceBase] (DirectAgent-3:ctx-e1c8a985) Copying 
/home/lungati/workspace/apache-cloudstack-4.4.2-src/client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xenserver/xcposs/vmops
 to 
/home/lungati/workspace/apache-cloudstack-4.3.2-src/scripts/vm/hypervisor/xenserver
 on 192.168.56.10 with permission 0755
2015-04-02 13:04:45,865 DEBUG [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-3:ctx-e1c8a985) Unable to create destination path: 
/home/lungati/workspace/apache-cloudstack-4.3.2-src/scripts/vm/hypervisor/xenserver
 on 192.168.56.10 but trying anyway
2015-04-02 13:04:45,873 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-3:ctx-e1c8a985) Unable to setup
...
Caused by: java.io.IOException: Remote scp terminated with error (scp: 
/home/lungati/workspace/apache-cloudstack-4.3.2-src/scripts/vm/hypervisor/xenserver:
 No such file or directory).
        at com.trilead.ssh2.SCPClient.readResponse(SCPClient.java:59)
        at com.trilead.ssh2.SCPClient.sendFiles(SCPClient.java:166)
        at com.trilead.ssh2.SCPClient.put(SCPClient.java:588)





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to