Upgrade from gitlab:16.2.8 to gitlab:16.3.0 fails

Cannot upgrade from 16.2.8 to 16.3.0

Is anyone having a similar issue?

1st error From docker logs

2023-10-09 14:25:16,942 INFO gave up: sshd entered FATAL state, too many start retries too quickly
/home/git/gitlab/lib/gitlab/instrumentation/redis.rb:9: warning: already initialized constant Gitlab::Instrumentation::Redis::ActionCable
/home/git/gitlab/lib/gitlab/instrumentation/redis.rb:9: warning: previous definition of ActionCable was here
rake aborted!
StandardError: An error has occurred, all later migrations canceled:

PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "postgres_async_foreign_key_validations_pkey"
DETAIL: Key (id)=(9) already exists.
/home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/connection_adapters/postgresql_adapter.rb:768:in exec_params' /home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activerecord-7.0.6/lib/active_record/connection_adapters/postgresql_adapter.rb:768:in block (2 levels) in exec_no_cache'
/home/git/gitlab/vendor/bundle/ruby/3.0.0/gems/activesupport-7.0.6/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'

Start with the Docker upgrade logs and the PostgreSQL migration failure in the reported output. Investigate the duplicate key on postgres_async_foreign_key_validations_pkey and the related ActiveRecord stack trace; done means the upgrade from gitlab:16.2.8 to gitlab:16.3.0 completes without the migration error.