You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Rohit Yadav (JIRA)" <ji...@apache.org> on 2015/04/30 16:03:06 UTC
[jira] [Closed] (CLOUDSTACK-4411) AWS API installation broken in
4.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohit Yadav closed CLOUDSTACK-4411.
-----------------------------------
Resolution: Won't Fix
very old issue, not seen now
> AWS API installation broken in 4.1
> ----------------------------------
>
> Key: CLOUDSTACK-4411
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4411
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: AWSAPI
> Affects Versions: 4.1.0
> Environment: CS 4.1 upgraded from 4.0.2 using (deb http://cloudstack.apt-get.eu/ubuntu precise 4.1)
> Ubuntu 12.04
> Reporter: Carlos Reategui
>
> After upgrading from 4.0.2 to 4.1 I installed aws-api with:
> $ apt-get install cloudstack-awsapi
> I ran into the following bugs in the AWS API installation:
> 1) Wrong permissions for awsapi log path.
> To fix do the following::
> $ chgrp cloud /var/log/cloudstack/awsapi;
> $ chmod g+w /var/log/cloudstack/awsapi
> 2) cloud-bridge db not created:
> To fix I found: /usr/share/cloudstack-bridge/setup/deploy-db-bridge.sh and ran it. However it reset my cloud PW so I had to set it back to what I had for the other processes to work.
> 3) Can't find: crypto.properties xes.keystore
> Installer moved them to /etc/cloudstack/management/ so I moved them back to /usr/share/cloudstack-management/webapps7080/awsapi/WEB-INF/classes/. It now starts.
> 4) Can not find end point reference.
> I am still stuck. cloudstack-aws-api-register appears to have worked but am now getting:
> Jul 31, 2013 3:54:41 PM org.apache.axis2.engine.AxisEngine receive SEVERE: The service cannot be found for the endpoint reference (EPR) http://localhost:7080/awsapi/services/AmazonEC2/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)