973984 - Datazilla Repository Update

Status: RESOLVED FIXED

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

Description

[Jonathan Eads ( :jeads )]

A new datazilla repository is ready to push to stage. This release includes the following changes:

1.) This modified repository fixes a recurring error when replicates are in the form of float values but are being cast to an int. This causes an uncaught ValueError to be raised. The int cast has been replaced with float https://github.com/mozilla/datazilla/blob/master/datazilla/model/base.py#L1321

Comment 1

[Chris Turra [:cturra]]

grabbing this. the admin node is currently in a pretty messy state because it's run out of inodes due to spooled mail jobs (/var/spool/postfix/maildrop/) from the datazilla cron. i am working on cleaning up those spool files then will do this push.

:jeads - we should spin off a separate discussion about this datazilla cron mail too.

Comment 2

[Chris Turra [:cturra]]

stage push complete and inode cleanup still in progress. let me know when you're happy with stage and i will push the changes out to prod.

Comment 3

[Jonathan Eads ( :jeads )]

I'm seeing an odd error on stage. 

AttributeError: 'Settings' object has no attribute 'ALLOWED_PROJECTS'

This would imply that the file datazilla/settings/local.py has been modified and no longer matches production. Might need to copy the local.py file from production to stage, the 'ALLOWED_PROJECTS' env variable should be defined.

Comment 4

[Chris Turra [:cturra]]

the ALLOWED_PROJECTS setting is identical between stage and prod.

[[e-mail]3 datazilla.allizom.org]# grep "ALLOWED_PROJECTS" /data/datazilla-stage/src/datazilla.allizom.org/datazilla/datazilla/settings/local.py
ALLOWED_PROJECTS = os.environ.get("ALLOWED_PROJECTS", "b2g|b2gtw|games|jetperf|pushlog|marketapps|microperf|stoneridge|talos|test|webpagetest")

[[e-mail]3 datazilla.allizom.org]# grep "ALLOWED_PROJECTS" /data/datazilla/src/datazilla.mozilla.org/datazilla/datazilla/settings/local.py
ALLOWED_PROJECTS = os.environ.get("ALLOWED_PROJECTS", "b2g|b2gtw|games|jetperf|pushlog|marketapps|microperf|stoneridge|talos|test|webpagetest")

Comment 5

[Jonathan Eads ( :jeads )]

I'm unable to reproduce the AttributeError in comment 3. It seems to have only occurred once, I'm guessing something in the push to stage was not initialized when I started testing. Please go ahead and push this to production.

Comment 6

[Chris Turra [:cturra]]

push to prod complete.

[[e-mail]3 datazilla.mozilla.org]# bash -x update
+ CODE_DIR=/data/datazilla/src/datazilla.mozilla.org/datazilla
+ VENDOR_DIR=/data/datazilla/src/datazilla.mozilla.org/datazilla/vendor
+ update_code
+ echo -e 'Updating code...'
Updating code...
+ cd /data/datazilla/src/datazilla.mozilla.org/datazilla
+ git fetch origin -q
+ checkretval
+ retval=0
+ [[ 0 -gt 0 ]]
+ git checkout -f origin/master -q
+ checkretval
+ retval=0
+ [[ 0 -gt 0 ]]
+ git submodule sync -q
+ checkretval
+ retval=0
+ [[ 0 -gt 0 ]]
+ git submodule update --init --recursive -q
+ checkretval
+ retval=0
+ [[ 0 -gt 0 ]]
+ echo -e 'Cleaning gitignore and pyc files...'
Cleaning gitignore and pyc files...
+ cd /data/datazilla/src/datazilla.mozilla.org/datazilla
+ find . -type f -name .gitignore -or -name '*.pyc' -delete
+ checkretval
+ retval=0
+ [[ 0 -gt 0 ]]
+ echo -e 'Storing revision information...'
Storing revision information...
+ cd /data/datazilla/src/datazilla.mozilla.org/datazilla
+ git rev-parse HEAD
update: line 40: /data/datazilla/src/datazilla.mozilla.org/datazilla/media/revision: No such file or directory
+ generate_revision_info
update: line 43: /data/datazilla/src/datazilla.mozilla.org/datazilla/media/revision_info.txt: No such file or directory
+ echo -e 'Deploying code...'
Deploying code...
+ '[' xterm == dumb ']'
+ /data/datazilla/deploy datazilla.mozilla.org