NoMethodError: undefined method `create' for #<Gitlab::Seeder::ComplianceDashboardMergeRequests>

When setting up a brand new GDK instance, the db:seed_fu tasks fails on ee/db/fixtures/development/32_compliance_dashboard_merge_requests.rb with the following:

$ gdk install
-- snip --
== Seed from ee/db/fixtures/development/32_compliance_dashboard_merge_requests.rb
rake aborted!
NoMethodError: undefined method `create' for #<Gitlab::Seeder::ComplianceDashboardMergeRequests:0x00007feaa16f9f80>
(eval):13:in `admin'
(eval):62:in `block in create_merge_request!'
/private/tmp/gitlab-development-kit/gitlab/config/initializers/forbid_sidekiq_in_transactions.rb:8:in `skipping_transaction_check'
(eval):61:in `create_merge_request!'
(eval):48:in `block in merge_requests'
(eval):40:in `map'
(eval):40:in `merge_requests'
(eval):19:in `seed!'
(eval):111:in `block (4 levels) in run_file'
(eval):109:in `each'
(eval):109:in `block (3 levels) in run_file'
/private/tmp/gitlab-development-kit/gitlab/lib/gitlab/seeder.rb:91:in `block in quiet'
/private/tmp/gitlab-development-kit/gitlab/lib/gitlab/seeder.rb:122:in `without_statement_timeout'
/private/tmp/gitlab-development-kit/gitlab/lib/gitlab/seeder.rb:90:in `quiet'
(eval):102:in `block (2 levels) in run_file'
/private/tmp/gitlab-development-kit/gitlab/lib/tasks/gitlab/setup.rake:34:in `setup_db'
/private/tmp/gitlab-development-kit/gitlab/lib/tasks/gitlab/setup.rake:5:in `block (2 levels) in <main>'
/private/tmp/gitlab-development-kit/gitlab/lib/tasks/dev.rake:7:in `block (2 levels) in <main>'
/Users/ash/.asdf/installs/ruby/2.6.6/bin/bundle:23:in `load'
/Users/ash/.asdf/installs/ruby/2.6.6/bin/bundle:23:in `<main>'
Tasks: TOP => db:seed_fu
(See full trace by running task with --trace)
support/bootstrap-rails failed
make: *** [postgresql-seed-rails] Error 1
❌️ ERROR: Failed to install.

added backend typebug labels

mentioned in issue #262861 (closed)

changed milestone to %13.6

mentioned in merge request gitlab-development-kit!1617 (merged)

mentioned in merge request !45631 (merged)

@ashmckenzie @ahegyi this NoMethodError on create seems very similar to #245320 (closed), where we've got a different fixture file raising NoMethodError on allow.

Isn't this some sort of caching error? Do we cache permissions/policies somehow so it doesn't resolve it properly?

In: app/services/merge_requests/create_service.rb

 unless can?(current_user, :create_merge_request_from, @source_project) &&
          can?(current_user, :create_merge_request_in, @project)

mentioned in merge request !44513 (merged)

closed