-
Notifications
You must be signed in to change notification settings - Fork 10
relation "instance" does not exist #5
Comments
Are you sure that you created the database ?
|
You mean tsuru app-run --app postgresapi -- python manage.py upgrade_db Just did. It was not in the Readme. Now we moved a bit forward: tsuru app-run --app postgresapi -- python manage.py upgrade_db I will check where my mistake is and report back. |
It is in the Install service section. For your next problem, you're user may not be an administrator that is able to create roles and databases. |
You may want to fix the docs. tsuru run is not a valid command (heroic run is, though). You want to fix the Readme to: tsuru app-run --app postgresapi -- python manage.py upgrade_db Regarding the password: since it is a DEV box, I will share here the exact values I used during install: tsuru env-set -a postgresapi POSTGRESAPI_DATABASE=postgresapi tsuru env-set -a postgresapi POSTGRESAPI_SHARED_HOST=172.17.42.1 I will try psql to see if these really work or if I had a typo during the PostgreSQL setup. Thanks! |
Ah, it used to exist, but it's now |
pdAdmin lets me in fine, using postgresapi/postgresapi. And I see the postgresapi role: CREATE ROLE postgresapi LOGIN And this is what I see for the postgresadmin role: CREATE ROLE postgresadmin LOGIN Anything wrong there? |
Using pgAdmin again I was also able to connect using posgresadmin/postgresapi. So, it is not a password problem. Could it be bad role defaults? |
I guess I need to go to the database and manually tweak the roles, just as I had to do with the mysqlapi? (tsuru/mysqlapi#35) tsuru service-add postgresapi namoroondb Any idea on what exactly I need to tweak on the database? Thanks! |
@sglebs the |
I followed the documented steps but I get this error when trying to create the service instance:
tsuru service-add postgresapi namoroondb
Error: Failed to create the instance namoroondb: relation "instance" does not exist
LINE 1: SELECT 1 FROM instance WHERE name='namoroondb'
Any ideas? Thanks!
The text was updated successfully, but these errors were encountered: