#pipeline trigger issue

15 messages · Page 1 of 1 (latest)

fluid bay
steel hatch
#
"ActiveRecord::NotNullViolation","exception.message":"PG::NotNullViolation: ERROR:  null value in column \"partition_id\" of relation \"ci_pipelines_config\" violates not-null constraint\nDETAIL:  Failing row contains (22369, ---\ninclude:\n- local: \".gitlab-ci.yml\"\n, null).\n","exception.backtrace":

This is the error I would be concerned about, did you do any maintenance on your Postgres Database? Even minimal maintenance?

fluid bay
#

I did a gitlab-ctl pg-upgrade yesterday.

#

also all migrations have been successful

#

any other pointers, what you mean by minimal database maintenance? The only other option I see, that I haven't used so far, would be the reindex command of rake.

steel hatch
#

can you send that rake command so I can see what it does before I recommend it?

#

By minimal I've seen database corruption occur with pointing to a new patroni leader...

#

but in 20 years of working in IT and with databases i've seen a lot.

fluid bay
#

the internal doc says this:

#

rake gitlab:db:reindex # Reindex database without downtime to eliminate bloat

steel hatch
#

You could try it and see if that fixes the issue.

fluid bay
#

fingers crossed

fluid bay
#

gitlab-rake gitlab:db:reindex
This feature (database_reindexing) is currently disabled.

fluid bay
fluid bay
#

solved by another restart of puma and sidekiq.