Project export error: private method `open' called for URI::Generic

Summary

When exporting a project, I consistently receive the error private method 'open' called for #<URI::Generic:0x00007f927520b1d8> in the response email.

Steps to reproduce

  1. Go to project Settings > General > Advanced > Export project.
  2. Receive an email with the above error.

Or:

Start the rails console:

sudo gitlab-rails console

and run:

p = Project.find_by_full_path('group-abc/project-xyz')
u = User.find_by_username('thangamuthu')
::Projects::ImportExport::ExportService.new(p, u).execute

What is the current bug behavior?

I receive an email:

Project Projects couldn't be exported.
The errors we encountered were:
• private method `open' called for #URI::Generic:0x00007f927520b1d8 —

What is the expected correct behavior?

Receive an email with a link to project export archive.

Relevant logs and/or screenshots

Output of ::Projects::ImportExport::ExportService.new(p, u).execute:

irb(main):003:0> ::Projects::ImportExport::ExportService.new(p, u).execute
Import/Export - Project Projects with ID: 55 export error - private method `open' called for #<URI::Generic:0x00007f7ca5206cb8>
Enqueued ActionMailer::DeliveryJob (Job ID: 7b294a38-ddcd-4fe6-a9c2-d252f6268678) to Sidekiq(mailers) with arguments: "Notify", "project_was_not_exported_email", "deliver_now", #<GlobalID:0x00007f7ca64fb1c0 @uri=#<URI::GID gid://gitlab/User/3>>, #<GlobalID:0x00007f7ca64fa8d8 @uri=#<URI::GID gid://gitlab/Project/55>>, ["private method `open' called for #<URI::Generic:0x00007f7ca5206cb8>"]
Traceback (most recent call last):
        4: from (irb):3
        3: from app/services/projects/import_export/export_service.rb:9:in `execute'
        2: from app/services/projects/import_export/export_service.rb:28:in `save_all!'
        1: from app/services/projects/import_export/export_service.rb:75:in `cleanup_and_notify_error!'
Gitlab::ImportExport::Error (private method `open' called for #<URI::Generic:0x00007f7ca5206cb8>)

Results of GitLab environment info

Using latest version of GitLab (12.2.5)

Expand for output related to GitLab environment info 
System information
System:         RedHatEnterpriseServer 7.2
Current User:   git
Using RVM:      no
Ruby Version:   2.6.3p62
Gem Version:    2.7.9
Bundler Version:1.17.3
Rake Version:   12.3.2
Redis Version:  3.2.12
Git Version:    2.22.0
Sidekiq Version:5.2.7
Go Version:     unknown

GitLab information
Version:        12.2.5
Revision:       09f8edbc29a
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     10.9
URL:            (private instance)
HTTP Clone URL: (private instance)
SSH Clone URL:  (private instance)
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: azure_oauth2


GitLab Shell
Version:        9.3.0
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check 
$ sudo gitlab-rake gitlab:check SANITIZE=true
Checking GitLab subtasks ...

Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 9.3.0 ? ... OK (9.3.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Check GitLab API access: OK
Redis available via internal API: OK


Access to /var/opt/gitlab/.ssh/authorized_keys: OK
gitlab-shell self-check successful


Checking GitLab Shell ... Finished


Checking Gitaly ...


Gitaly: ... default ... OK


Checking Gitaly ... Finished


Checking Sidekiq ...


Sidekiq: ... Running? ... yes
Number of Sidekiq processes ... 1


Checking Sidekiq ... Finished


Checking Incoming Email ...


Incoming Email: ... Reply by email is disabled in config/gitlab.yml


Checking Incoming Email ... Finished


Checking LDAP ...


LDAP: ... LDAP is disabled in config/gitlab.yml


Checking LDAP ... Finished


Checking GitLab App ...


Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... skipped (omnibus-gitlab has no init script)
Init script up-to-date? ... skipped (omnibus-gitlab has no init script)
Projects have namespace: ...
6/3 ... yes
6/12 ... yes
6/13 ... yes
6/14 ... yes
6/15 ... yes
6/16 ... yes
6/17 ... yes
6/18 ... yes
6/19 ... yes
6/20 ... yes
6/21 ... yes
23/22 ... yes
11/25 ... yes
11/26 ... yes
6/27 ... yes
6/28 ... yes
6/29 ... yes
6/30 ... yes
6/31 ... yes
2/35 ... yes
2/36 ... yes
6/37 ... yes
6/40 ... yes
6/41 ... yes
6/42 ... yes
6/43 ... yes
6/45 ... yes
23/46 ... yes
23/47 ... yes
23/48 ... yes
23/49 ... yes
23/50 ... yes
23/51 ... yes
23/53 ... yes
38/55 ... yes
39/56 ... yes
6/57 ... yes
4/58 ... yes
6/59 ... yes
6/60 ... yes
6/61 ... yes
4/62 ... yes
54/63 ... yes
6/64 ... yes
54/65 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.3)
Git version >= 2.22.0 ? ... yes (2.22.0)
Git user has default SSH configuration? ... yes
Active users: ... 10


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Possible fixes

I am running this export on a project that only uses issues and no other project features and it consistently fails. The project has about 1300 issues with comments, images and attachments. I am able to successfully run an export on another project on this instance. I suspect that this may have something to do with content of an issue or comment somewhere in this project, but the stacktrace doesn't give enough information to pinpoint where.