Hi Jakob,
After reading around the docs Patrick linked, I noticed that both
Feature.enabled?(:execute_batched_migrations_on_schedule)
and
Feature.enabled?(:optimize_batched_migrations)
returned false.
I just checked these settings for me and both returned true. I manually
restarted the
I have not upgraded to 15.0.4 yet but found the following jobs being
in failed state on my instance:
id | status | job_class_name | table_name |
column_name | job_arguments
++++-+---
Hi Patrick,
Your issue seems to be the same as Bug#1015301 that I just filed earlier
today.
I actually shared a workaround that allowed me to finish the upgrade by
temporarily marking the failed background migrations as successful in
the database. Maybe you wanna have a look there:
2022, ജൂലൈ 19 12:05:37 PM GMT+02:00, "Patrick Matthäi" ൽ
എഴുതി
>Package: gitlab
>Version: 15.0.4+ds1-1
>Severity: serious
>
>Hey,
>
>on upgrading gitlab I always end up with this error:
>
>(1055 rows) = Did not find any relations. ]
>+ echo gitlab_production database is not empty, skipping
4 matches
Mail list logo
