"Failed to process image" when attempting to upload into a comment

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Summary

When attempting to add an image to a comment on an issue, an error messages is shown in the corner of the editor.

Steps to reproduce

1. Open up an issue
2. In the comments, attempt to embed an image (such as by clicking and dragging).
3. 

Example Project

N/A - this has been reproduced on different projects in this environment.

What is the current bug behavior?

The error, and the image does not get embedded.

What is the expected correct behavior?

The image should be embedded.

Relevant logs and/or screenshots

This is a random image that failed to upload. Interestingly, it uploads here. (I've uploaded it as a zip file so that it gets preserved) FJe0NaZjjAk4lPlu_F8xLkRtdfxspDMMY8g1GDFingo.zip

Although the front-end error doesn't tell us much, I did find this in the logs;

==> /var/log/gitlab/gitlab-workhorse/current <==
{"correlation_id":"01G9NHRWER4WFG5T8PQGQ592K3","filename":"FJe0NaZjjAk4lPlu_F8xLkRtdfxspDMMY8g1GDFingo.jpg","level":"info","msg":"running exiftool to remove any metadata","time":"2022-08-04T23:06:42Z"}
{"content_type":"","correlation_id":"01G9NHRWY0TPX4R1RT0S3XWTTC","duration_ms":0,"host":"git.skhuf.net","level":"info","method":"POST","msg":"access","proto":"HTTP/1.1","referrer":"","remote_addr":"127.0.0.1:0","remote_ip":"127.0.0.1","route":"^/api/v4/jobs/request\\z","status":204,"system":"http","time":"2022-08-04T23:06:43Z","ttfb_ms":0,"uri":"/api/v4/jobs/request","user_agent":"gitlab-runner 15.2.1 (15-2-stable; go1.17.9; linux/amd64)","written_bytes":0}

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

I'm using docker, currently gitlab is at version 15.2.1-ee.

```
System information
System:
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.7.5p203
Gem Version:    3.1.4
Bundler Version:2.3.15
Rake Version:   13.0.6
Redis Version:  6.2.7
Sidekiq Version:6.4.0
Go Version:     unknown
```

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.9.0 ? ... OK (14.9.0)
Running /opt/gitlab/embedded/service/gitlab-shell/bin/check
Internal API available: OK
Redis available via internal API: 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 (cluster/worker) ... 1/1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Checking Reply by email ...

IMAP server credentials are correct? ... Checking git@skhuf.net
yes
Mailroom enabled? ... skipped
MailRoom running? ... skipped

Checking Reply by email ... Finished


Checking Incoming Email ... Finished

Checking LDAP ...

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

Checking LDAP ... Finished

Checking GitLab App ...

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
Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units)
Projects have namespace: ... 
3/1 ... yes
4/2 ... yes
4/3 ... yes
3/4 ... yes
3/5 ... yes
3/6 ... yes
3/7 ... yes
8/9 ... yes
9/10 ... yes
8/11 ... yes
2/12 ... yes
4/13 ... yes
10/14 ... yes
2/15 ... yes
10/17 ... yes
8/18 ... yes
2/19 ... yes
10/20 ... yes
10/21 ... yes
10/22 ... yes
6/23 ... yes
2/24 ... yes
6/25 ... yes
6/26 ... yes
3/28 ... yes
3/29 ... yes
10/30 ... yes
10/31 ... yes
3/32 ... yes
10/33 ... yes
2/34 ... yes
2/35 ... yes
6/36 ... yes
2/37 ... yes
2/38 ... yes
10/39 ... yes
2/40 ... yes
25/41 ... yes
2/42 ... yes
3/43 ... yes
24/44 ... yes
3/45 ... yes
24/46 ... yes
2/48 ... yes
3/49 ... yes
3/50 ... yes
3/51 ... yes
10/52 ... yes
2/53 ... yes
2/54 ... yes
2/55 ... yes
2/56 ... yes
2/57 ... yes
3/58 ... yes
3/60 ... yes
2/61 ... yes
2/62 ... yes
3/63 ... yes
2/64 ... yes
10/65 ... yes
2/66 ... yes
24/67 ... yes
Redis version >= 6.0.0? ... yes
Ruby version >= 2.7.2 ? ... yes (2.7.5)
Git user has default SSH configuration? ... yes
Active users: ... 15
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... yes
Elasticsearch version 7.x-8.x or OpenSearch version 1.x ... skipped (Advanced Search is disabled)

Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes