Migrations chart failures (2018-02-05)
The last several merges to master
branch have resulted in failed deploys. This appears to be due to problems with the migrations
Job. The result is that no environment will successfully deploy, as the job continually is restarted.
Details:
In production
environment, I am seeing the following errors in the migrations
job log:
Caused by:
ActiveRecord::StatementInvalid: PG::UndefinedColumn: ERROR: column "closed_at_for_type_change" does not exist
LINE 1: SELECT "issues"."id" FROM "issues" WHERE (closed_at_for_typ...
^
: SELECT "issues"."id" FROM "issues" WHERE (closed_at_for_type_change IS NULL AND closed_at IS NOT NULL) ORDER BY "issues"."id" ASC LIMIT 1
...
(See full trace by running task with --trace)
== 20180201145907 MigrateRemainingIssuesClosedAt: migrating ===================
-- columns("issues")
-> 0.0019s
In !112 (merged) , I am seeing
/home/git/gitlab/vendor/bundle/ruby/2.3.0/gems/railties-4.2.10/lib/rails/commands/runner.rb:62:in '<top (required)>': undefined local variable or method 'current_application_settings' for main:Object (NameError)