Error while database seeding on empty external postgres for GitLab 16.6.1

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

  • Close this issue

Summary

Similar to other ticket i.e. #404766 (closed) the GitLab version 16.6.1 is trying to seed on empty postgres database and it gives error in postgres log but doesn't fail.

Steps to reproduce

  1. Run Postgres database container with version 16.1 and create a empty database named gitlabhq_production
  2. Run Redis container with version 7.2.3.
  3. Use the address, port, username and password of both components in Omnibus GitLab container of version 16.6.1.
  4. So once it start db:schema:load rake task it will seed the tables, schema in postgres database and if you observe the logs of postgres carefully you will see the same error mentioned in the linked ticket.

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

ERROR:  relation "feature_gates" does not exist at character 491
STATEMENT:  SELECT a.attname, format_type(a.atttypid, a.atttypmod),
	       pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod,
	       c.collname, col_description(a.attrelid, a.attnum) AS comment,
	       attgenerated as attgenerated
	  FROM pg_attribute a
	  LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum
	  LEFT JOIN pg_type t ON a.atttypid = t.oid
	  LEFT JOIN pg_collation c ON a.attcollation = c.oid AND a.attcollation <> t.typcollation
	 WHERE a.attrelid = '"feature_gates"'::regclass
	   AND a.attnum > 0 AND NOT a.attisdropped
	 ORDER BY a.attnum
Edited Sep 08, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading