https://dagster.io/ logo
#announcements
Title
# announcements
c

Cris

06/13/2020, 7:00 PM
My repo.py is structured like this,
m

max

06/13/2020, 10:40 PM
@sashank @prha
s

sashank

06/15/2020, 2:51 PM
And what does your
workspace.yaml
look like?
c

Cris

06/15/2020, 2:51 PM
Copy code
load_from:
  - python_file: repository.py
Just that, it seemed to be a problem with the migration. I havent managed to execute the migration correctly, but it works when I used a new Postgres DB
s

sashank

06/15/2020, 2:53 PM
Is this similar to what you saw https://github.com/dagster-io/dagster/issues/2601?
cc @alex
c

Cris

06/15/2020, 2:55 PM
Hm, not quite, i had this error
Copy code
sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedTable) relation "runs" does not exist

[SQL: ALTER TABLE runs ADD COLUMN snapshot_id VARCHAR(255)]
Running the migration with this command
Copy code
$ PYTHONPATH=$PYTHONPATH:${PWD}/app DAGSTER_HOME=~/dagster/dagster_home dagster instance migrate
p

prha

06/15/2020, 3:45 PM
In your
dagster.yaml
, is your instance configured to use the same postgres DB for runs, event_log, and schedule storage or different DBs? Has that changed recently?
There’s an issue in one of our migration scripts, but just want to make sure the fix will unblock you…
c

Cris

06/15/2020, 3:55 PM
In the configuration on which I tried the migration the dbs are different. In production we have a single RDS instance.
p

prha

06/15/2020, 4:19 PM
Okay, perfect… we’ll get a fix out for this today
c

Cris

06/15/2020, 4:20 PM
Thanks! I'm still confused on whether the bug happens when you use multiple or single dbs?
p

prha

06/15/2020, 4:21 PM
The bug happens when you use multiple DBs… we were missing a check to make sure that a migration only happens on the runs storage
c

Cris

06/15/2020, 4:21 PM
oh I see
p

prha

06/15/2020, 11:06 PM
This should be resolved in
0.8.2
. Lemme know if you are still seeing issues running
dagster instance migrate
c

Cris

06/16/2020, 2:55 PM
Thanks, will try