500 when adding email to a user on staging.gitlab.com

Summary

500 when adding email to a user on staging.gitlab.com

Steps to reproduce

1. Loging to staging.gitlab.com
2. Click the user's avatar > Settings > Emails
3. Add a new email address

Example Project

N/A

What is the current bug behavior?

500 shown.

What is the expected correct behavior?

New email is added.

Relevant logs and/or screenshots

Kibana: https://nonprod-log.gitlab.net/goto/f1e772b3a90b888a66913468eec581d6

        "app/services/emails/create_service.rb:8:in `execute'",
        "ee/app/services/ee/emails/create_service.rb:10:in `execute'",
        "app/controllers/profiles/emails_controller.rb:12:in `create'",
        "ee/lib/gitlab/ip_address_state.rb:10:in `with'",
        "ee/app/controllers/ee/application_controller.rb:43:in `set_current_ip_address'",
        "app/controllers/application_controller.rb:482:in `set_current_admin'",
        "lib/gitlab/session.rb:11:in `with_session'",
        "app/controllers/application_controller.rb:473:in `set_session_storage'",
        "app/controllers/application_controller.rb:467:in `set_locale'",
        "lib/gitlab/error_tracking.rb:48:in `with_context'",
        "app/controllers/application_controller.rb:562:in `sentry_context'",
        "lib/gitlab/application_context.rb:52:in `block in use'",
        "lib/gitlab/application_context.rb:52:in `use'",
        "lib/gitlab/application_context.rb:20:in `with_context'",
        "app/controllers/application_controller.rb:458:in `set_current_context'",
        "ee/lib/omni_auth/strategies/group_saml.rb:41:in `other_phase'",
        "ee/lib/gitlab/jira/middleware.rb:19:in `call'"

Output of checks

This bug happens on staging.gitlab.com running 13.0.0-pre e1504bb5 (as of creating this bug)

Does not happen on local.