Gitlab-ce email problem after upgrade 17.5.5 to 17.10.1

How to Use GitLab Self-managed
1

After update gitlab-ce from 17.5.5 to 17.10.1 email sending don’t work. I check from rails-console and get error:
irb(main):002:0> Notify.test_email(‘xxx@xxx.xxx’, ‘Test’, ‘Test’).deliver_now
(irb):2:in <main>': undefined local variable or method ‘y’ for main:Object (NameError)
from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/railties-7.0.8.7/lib/rails/commands/console/console_command.rb:74:in start' from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/railties-7.0.8.7/lib/rails/commands/console/console_command.rb:19:in start’
from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/railties-7.0.8.7/lib/rails/commands/console/console_command.rb:106:in perform' from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/thor-1.3.1/lib/thor/command.rb:28:in run’
from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/thor-1.3.1/lib/thor/invocation.rb:127:in invoke_command' from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/thor-1.3.1/lib/thor.rb:527:in dispatch’
from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/railties-7.0.8.7/lib/rails/command/base.rb:87:in perform' from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/railties-7.0.8.7/lib/rails/command.rb:48:in invoke’
from /opt/gitlab/embedded/lib/ruby/gems/3.2.0/gems/railties-7.0.8.7/lib/rails/commands.rb:18:in <top (required)>' from <internal:/opt/gitlab/embedded/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:37:in require’
from internal:/opt/gitlab/embedded/lib/ruby/site_ruby/3.2.0/rubygems/core_ext/kernel_require.rb:37:in require' from bin/rails:4:in ’

Also i try check email sending via password recovery and get this message “If your email address exists in our database, you will receive a password recovery link at your email address in a few minutes.” but no any connect attemp in my mail server. No any changes in settings during upgrade.

Steps to reproduce

Send test letter via rail-console.

Configuration

GitLab versionv17.10.1

GitLab Shell14.41.0

GitLab Workhorsev17.10.1

GitLab APIv4

GitLab KASv17.10.1 v17.10.1

Ruby3.2.5p208

Rails7.0.8.7

PostgreSQL (main)14.17

PostgreSQL (ci)14.17

Redis7.0.15

Versions

Versions
System information
System: Debian 12
Current User: git
Using RVM: no
Ruby Version: 3.2.5
Gem Version: 3.6.5
Bundler Version:2.6.5
Rake Version: 13.0.6
Redis Version: 7.0.15
Sidekiq Version:7.2.4
Go Version: unknown

GitLab information
Version: 17.10.1
Revision: 5ef58a00091
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 14.17
URL:
HTTP Clone URL:
SSH Clone URL:
Using LDAP: yes
Using Omniauth: yes
Omniauth Providers:

GitLab Shell
Version: 14.41.0
Repository storages:

  • default: unix:/var/opt/gitlab/gitaly/gitaly.socket
    GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell

Gitaly

  • default Address: unix:/var/opt/gitlab/gitaly/gitaly.socket
  • default Version: 17.10.1
  • default Git Version: 2.48.1.gl1
3

Hi there,

I haven’t replicate this issue yet but just going from what I see from the details provided, are the SMTP settings correct in /etc/gitlab/gitlab.rb ?

it seems email doesn’t work from irb and gitlab-rails, is that correct ? have you sudo tail -f /var/log/gitlab/gitlab-rails/production.log is there any Sidekiq jobs running at all ?

Cheers,

4

Hi.
SMTP settings in gitlab.rb is correct, i don’t change it during updates. I recheck mail delivery and detect what ordinary mail was delivered normally. But test via rail-console unsucsessful.