[
https://issues.apache.org/jira/browse/CLOUDSTACK-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13605884#comment-13605884
]
Prachi Damle commented on CLOUDSTACK-1713:
------------------------------------------
Pradeep,
I found the problem causing the db permissions error. In the
cloudstack-setup-databases I see cloudbridge_db.sql is getting called. So that
is be the problem.
What I see is, as you had mentioned previously, db.properties is present at two
locations
[root@Rack3Host23 ~]# find / -name db.properties
/usr/share/cloudstack-bridge/webapps/bridge/WEB-INF/classes/db.properties
/etc/cloudstack/management/db.properties
Now I did this:
1) I removed this
/usr/share/cloudstack-bridge/webapps/bridge/WEB-INF/classes/db.properties
2) I removed log4j-vmops.xml
3) I moved over all the *.properties, *.xml and xes.keystore files to
/etc/cloudstack/management
4) I restarted cloudstack
After restart, I no longer see the db permissions or driver errors in awsapi.log
So can you fix the packaging to include all the awsapi configuration files in
/etc/cloudstack/management and no file should be put under
/usr/share/cloudstack-bridge/webapps/bridge/WEB-INF/classes/ ?
You can check Chandan's setup to see the list of configuration files needed
under /etc/cloudstack/management
> EC2 REST API: AWS API Installation Problems
> -------------------------------------------
>
> Key: CLOUDSTACK-1713
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1713
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.1.0, 4.2.0
> Reporter: Chandan Purushothama
> Assignee: Pradeep Soundararajan
> Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> Further bug report conversations of CS-1557 will be done here. Since the bug
> CS-1557 was initially filed for missing cloudbridge database, I filed this
> bug to keep track of other issues related to aws-api installation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
