19913d85-f662-4518-a9a1-7adc1793dfd4.png){kind=small}
My repo.py is structured like this,
# announcementsc
Cris
06/13/2020, 7:00 PMMy repo.py is structured like this,
m
max
06/13/2020, 10:40 PM@sashank @prha
s
sashank
06/15/2020, 2:51 PMAnd what does your
workspace.yamlc
Cris
06/15/2020, 2:51 PM Copy code
load_from:
- python_file: repository.pyCris
06/15/2020, 2:52 PMJust 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 PMIs this similar to what you saw https://github.com/dagster-io/dagster/issues/2601?
sashank
06/15/2020, 2:54 PMcc @alex
c
Cris
06/15/2020, 2:55 PMHm, 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)]Cris
06/15/2020, 2:56 PMRunning the migration with this command
Copy code
$ PYTHONPATH=$PYTHONPATH:${PWD}/app DAGSTER_HOME=~/dagster/dagster_home dagster instance migratep
prha
06/15/2020, 3:45 PMIn your
dagster.yamlprha
06/15/2020, 3:47 PMThere’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 PMIn 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 PMOkay, perfect… we’ll get a fix out for this today
c
Cris
06/15/2020, 4:20 PMThanks! I'm still confused on whether the bug happens when you use multiple or single dbs?
p
prha
06/15/2020, 4:21 PMThe 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 PMoh I see
p
prha
06/15/2020, 11:06 PMThis should be resolved in
0.8.2dagster instance migratec
Cris
06/16/2020, 2:55 PMThanks, will try