1408800 - Production db dump doesn't contain any release data

Status: RESOLVED FIXED

(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P1)

Description

[Nick Thomas [:nthomas] (UTC+12)]

Attachment: prod_db_dump.sql.zst

I grabbed https://balrog-public-dump-prod.s3.amazonaws.com/dump.sql.txt and got 81301417 bytes (hash 40a9be8f30b73f362c3d00fc484a1a1675a25c59, see attachment). After removing .cache and starting up Balrog there are rules but not releases.

$ grep 'INSERT INTO' prod_db_dump.sql | cut -c 1-80 | grep -v releases_history
INSERT INTO `dockerflow` VALUES (16);
INSERT INTO `rules` VALUES (1,300,'No-Update',100,'minor','Firefox',NULL,'nightl
INSERT INTO `rules_history` VALUES (1,'[e-mail]',1,NULL,NULL,NULL,NU
INSERT INTO `rules_history` VALUES (5609,'[e-mail]',344,95,'OSX-10.6
INSERT INTO `migrate_version` VALUES ('balrog','scripts/../auslib/migrate',29);

Doesn't appear to be truncated, so a regression from bug 1376331 ?

Comment 1

[[e-mail] (:bhearsum)]

Looks like it. I'll get this fixed this week.

Comment 2

[[github robot]]

Commit pushed to master at https://github.com/mozilla/balrog

https://github.com/mozilla/balrog/commit/7f39e8b7de445c4bc4ab85b69a12eaddc59a9d38
bug 1408800: Production db dump doesn't contain any release data (#428). r=nthomas

Comment 3

[[e-mail] (:bhearsum)]

This fix hit production today - I'll have a look at the updated database dump tomorrow to make sure this is fixed.

Comment 4

[[e-mail] (:bhearsum)]

The latest push almost worked - except for a one character typo that I fixed in https://github.com/mozilla/balrog/commit/0f26a49ed3f33cbdc4232a30815a7da270ae3704. That fix will go to prod next week.

Comment 5

[[e-mail] (:bhearsum)]

This is fixed, finally.