1476807 - migrations failed on stage

Status: RESOLVED FIXED

(Socorro :: Infra, task)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

I got an email from datadog saying the migrations failed on stage:

"""
[i-04b6dfd2843caf9fa] socorro_run_migrations failed in 2.04s

>>>> CMD <<<<

/bin/docker run --rm --env-file /etc/dockerflow/crontabber.txt --log-driver=syslog --log-opt syslog-format=rfc3164 --log-opt syslog-address=udp://127.0.0.1:10514 hub.prod.mozaws.net/mozilla/socorro_crontabber:latest-384 /app/scripts/run_migrations.sh 

>>>> EXIT CODE <<<<

127

>>>> STDERR <<<<

container_linux.go:247: starting container process caused "exec: \"/app/scripts/run_migrations.sh\": stat /app/scripts/run_migrations.sh: no such file or directory"  
/usr/bin/docker-current: Error response from daemon: invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"exec: \\\"/app/scripts/run_migrations.sh\\\": stat /app/scripts/run_migrations.sh: no such file or directory\"\n".  
"""

The running theory is that this bumped into what Brian was doing with crontabber on stage.

This bug covers making sure migratinos are working.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

Tagging Brian because we think this might be related to his stuff.

Comment 2

[Brian Pitts]

I accidentally deployed an old version that doesn't have that script.

I have disarmed the footgun that defauled to deploying old versions, so this shouldn't happen again.