1030613 - [mozillians] re-run geocode migration

Status: VERIFIED FIXED

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

Description

[Andrei Hajdukewycz [:sancus]]

The mozillians geolocation migration failed on a bunch of profiles that it shouldn't have failed on. I tracked the problem down to an issue with the geodata.json file I uploaded. I'm going to upload a fixed data set in this bug, and the following steps will be needed on prod:

1) Download geocoding.json from this bug.
2) Run ./manage.py loaddata geocoding.json
3) Run the following sql on the database:
UPDATE profile SET geo_country_id=NULL WHERE geo_city_id IS NULL OR geo_region_id IS NULL;
4) Run ./manage.py geocode until it says there are 6 profiles left to geocode.

Comment 1

[Andrei Hajdukewycz [:sancus]]

Attachment: geocoding.json

Comment 2

[Andrei Hajdukewycz [:sancus]]

Oops, I forgot to mention a step. Before loading the data, run "truncate geo_geocoding" in the database. The modified steps follow:
1) Download geocoding.json from this bug.
2) Run sql on the db:
TRUNCATE geo_geocoding
3) Run ./manage.py loaddata geocoding.json
4) Run sql on the db:
UPDATE profile SET geo_country_id=NULL WHERE geo_city_id IS NULL OR geo_region_id IS NULL;
5) Run ./manage.py geocode until it says there are 6 profiles left to geocode.

After doing this, https://mozillians.org/en-US/country/United%20States/city/San%20Francisco/ should contain roughly 10 pages of results instead of only a few.

Comment 3

[Philippe M. Chiasson (:gozer)]

6 profiles left to geocode.

Comment 4

[Matt Brandt [:mbrandt]]

Bumping to QA verified -- results on prod look and behave correctly. Automated tests are passing again.