[
https://issues.apache.org/jira/browse/DTACLOUD-508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598681#comment-13598681
]
Michal Fojtik commented on DTACLOUD-508:
----------------------------------------
I do believe this error is fixed now in master, by using the 'initializers'.
The BASE_STORAGE directory is created
and correct permissions are set before the database is being initialized.
The workaround for this version could be to override the default database
location using:
$ DATABASE_LOCATION="sqlite:///tmp/db.sqlite" deltacloudd -i mock -f cimi
> Fresh detacloud install doesnt create database file
> ---------------------------------------------------
>
> Key: DTACLOUD-508
> URL: https://issues.apache.org/jira/browse/DTACLOUD-508
> Project: DeltaCloud
> Issue Type: Bug
> Components: CIMI/Frontend, Server
> Reporter: Carlos Goncalves
>
> Fresh install of Deltacloud v1.1.1 via rubygem o a clean gemset and running
> deltacloudd with CIMI frontend errors due to non existent database file. No
> earlier Deltacloud installed on this machine.
> Deltacloud doesn't create file /var/tmp/deltacloud-$USER/db.sqlite.
> SQLite3::CantOpenException: unable to open database file
> (Sequel::DatabaseConnectionError)
> Errors like that^ will be probably related to this issue.
> Checking out Deltacloud from Git and running deltacloud-db-upgrade followed
> by deltacloudd will do. Still, even with the database file created, can't run
> v1.1.1.
--
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
