1030929 - [mozillians] Fix database migration for "Country Error"

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Engagement, task)

Description

[Andrei [:sancus]]

Somehow the database migration that adds a "Country Error" record to the database didn't run properly on prod. It ran properly on dev/stage *shrug*. Lets just cycle it.

1) ./manage.py migrate geo 0003
2) ./manage.py migrate geo 

And done!

To confirm it's there you can run sql:
select * from geo_country where code='xx';

which should output:

+-----+---------------+------+-----------+
| id  | name          | code | mapbox_id |
+-----+---------------+------+-----------+
| 139 | Country Error | xx   | geo_error |
+-----+---------------+------+-----------+
1 row in set (0.00 sec)

Comment 1

[Chris Turra [:cturra]]

(In reply to Andrei Hajdukewycz [:sancus] from comment #0)
> 
> 1) ./manage.py migrate geo 0003
> 2) ./manage.py migrate geo 

i ran these as requested and this is the results on the database...

 mysql> select * from geo_country where code='xx';
 Empty set (0.00 sec)


look as expected?

Comment 2

[Andrei [:sancus]]

No.. it should be creating that row. I'm really confused why it wouldn't be able to...

Comment 3

[Andrei [:sancus]]

Manually creating this via the python shell worked. No idea why the migration didn't, but as long as this record is there, our error code should work.

Thanks.