Containerized omnibus deployment: Neither online view nor download of HTML artifacts working with gitlab pages enabled

Summary

I'm using gitlab-ee v11.0.4-ee.0 using containerized omnibus deployment.

Enabling gitlab pages breaks downloading HTML artifacts and leaves me with a defunct link to an online view of the artifact (502 - Whoops, something went wrong on our end.). Without gitlab pages I was at least able to download a html artifact from the artifacts browser (The source could not be displayed because it is stored as a job artifact. You can download it instead.).

In order to enable gitlab pages I had to configure gitlab_pages['inplace_chroot'] = true as described in gitlab-pages/#129. The ticket mentions, that this will break online view of html artifacts. It does not say however, that it will also break downloading html artifacts. Besides that, I'd expect pages to be fully usable when using containerized omnibus deployment.

Steps to reproduce

1. Setup gitlab-ee containerized omnibus deployment
2. Enable gitlab pages by adding pages_external_url configuration to GITLAB_OMNIBUS_CONIFG
3. Apply fix from gitlab-pages/#129: add gitlab_pages['inplace_chroot'] = true configuration to GITLAB_OMNIBUS_CONIFG
4. Start gitlab appliance
5. Setup the plain-html gitlab pages example in the newly created gitlab-ee instance
6. Open artifacts browser and click on the artifact named index.html
7. You'll get an error: 502 - Whoops, something went wrong on our end.

Example Project

Cannot be reproduced on gitlab.com as it needs a containerized omnibus deployment.

However, there's an example project that can be used to verify the issue locally: plain-html

What is the current bug behavior?

You'll get an error: 502 - Whoops, something went wrong on our end.

What is the expected correct behavior?

Either: The source could not be displayed because it is stored as a job artifact. You can download it instead.

Or better: An online view of the html artifact.

Relevant logs and/or screenshots

None.

Output of checks

None.

Results of GitLab environment info

Expand for output related to GitLab environment info

root@gitlab:/# gitlab-rake gitlab:env:info
System information
System:
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.4.4p296
Gem Version:    2.7.6
Bundler Version:1.16.2
Rake Version:   12.3.1
Redis Version:  3.2.11
Git Version:    2.17.1
Sidekiq Version:5.1.3
Go Version:     unknown
GitLab information
Version:        11.0.4-ee
Revision:       3350cd6
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
DB Version:     9.6.8
URL:            http://gitlab.episource.de
HTTP Clone URL: http://gitlab.episource.de/some-group/some-project.git
SSH Clone URL:  git@gitlab.episource.de:some-group/some-project.git
Elasticsearch:  yes
Geo:            no
Using LDAP:     no
Using Omniauth: no
GitLab Shell
Version:        7.1.4
Repository storage paths:
-- default:      /var/opt/gitlab/git-data/repositories
Hooks:          /opt/gitlab/embedded/service/gitlab-shell/hooks
Git:            /opt/gitlab/embedded/bin/git

Results of GitLab application Check

Expand for output related to the GitLab application check

root@gitlab:/# gitlab-rake gitlab:check SANITIZE=true
Checking GitLab Shell ...
GitLab Shell version >= 7.1.4 ? ... OK (7.1.4)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
4/3 ... ok
3/4 ... ok
8/5 ... ok
3/6 ... ok
3/7 ... ok
3/8 ... ok
3/9 ... ok
3/10 ... ok
3/11 ... ok
15/12 ... ok
3/13 ... ok
3/14 ... ok
3/15 ... ok
3/16 ... ok
3/17 ... ok
4/18 ... ok
6/19 ... ok
7/20 ... ok
3/23 ... ok
3/24 ... ok
3/25 ... ok
3/26 ... ok
3/27 ... ok
8/28 ... ok
8/29 ... ok
8/30 ... ok
2/31 ... ok
3/32 ... ok
3/33 ... ok
3/34 ... ok
3/35 ... ok
3/36 ... ok
7/37 ... ok
2/38 ... ok
17/39 ... ok
3/40 ... ok
3/41 ... ok
18/42 ... ok
5/43 ... ok
3/44 ... ok
3/45 ... ok
9/46 ... ok
9/47 ... ok
9/48 ... ok
3/49 ... ok
10/50 ... ok
3/51 ... ok
9/52 ... ok
5/53 ... ok
5/54 ... ok
5/56 ... ok
5/58 ... ok
12/59 ... ok
3/60 ... ok
3/61 ... ok
3/62 ... ok
5/63 ... ok
5/64 ... ok
5/65 ... ok
5/66 ... ok
4/67 ... ok
3/68 ... ok
5/69 ... ok
13/70 ... ok
13/71 ... ok
13/72 ... ok
13/73 ... ok
14/74 ... ok
7/75 ... ok
7/76 ... ok
7/77 ... ok
7/78 ... ok
7/79 ... ok
7/80 ... ok
7/81 ... ok
7/82 ... ok
7/83 ... ok
7/84 ... ok
7/85 ... ok
7/86 ... ok
7/87 ... ok
7/88 ... ok
7/89 ... ok
7/90 ... ok
7/91 ... ok
7/92 ... ok
5/93 ... repository is empty
5/94 ... ok
3/95 ... ok
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 Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Reply by email is disabled in config/gitlab.yml
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
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: ...
4/3 ... yes
3/4 ... yes
8/5 ... yes
3/6 ... yes
3/7 ... yes
3/8 ... yes
3/9 ... yes
3/10 ... yes
3/11 ... yes
15/12 ... yes
3/13 ... yes
3/14 ... yes
3/15 ... yes
3/16 ... yes
3/17 ... yes
4/18 ... yes
6/19 ... yes
7/20 ... yes
3/23 ... yes
3/24 ... yes
3/25 ... yes
3/26 ... yes
3/27 ... yes
8/28 ... yes
8/29 ... yes
8/30 ... yes
2/31 ... yes
3/32 ... yes
3/33 ... yes
3/34 ... yes
3/35 ... yes
3/36 ... yes
7/37 ... yes
2/38 ... yes
17/39 ... yes
3/40 ... yes
3/41 ... yes
18/42 ... yes
5/43 ... yes
3/44 ... yes
3/45 ... yes
9/46 ... yes
9/47 ... yes
9/48 ... yes
3/49 ... yes
10/50 ... yes
3/51 ... yes
9/52 ... yes
5/53 ... yes
5/54 ... yes
5/56 ... yes
5/58 ... yes
12/59 ... yes
3/60 ... yes
3/61 ... yes
3/62 ... yes
5/63 ... yes
5/64 ... yes
5/65 ... yes
5/66 ... yes
4/67 ... yes
3/68 ... yes
5/69 ... yes
13/70 ... yes
13/71 ... yes
13/72 ... yes
13/73 ... yes
14/74 ... yes
7/75 ... yes
7/76 ... yes
7/77 ... yes
7/78 ... yes
7/79 ... yes
7/80 ... yes
7/81 ... yes
7/82 ... yes
7/83 ... yes
7/84 ... yes
7/85 ... yes
7/86 ... yes
7/87 ... yes
7/88 ... yes
7/89 ... yes
7/90 ... yes
7/91 ... yes
7/92 ... yes
5/93 ... yes
5/94 ... yes
3/95 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.5 ? ... yes (2.4.4)
Git version >= 2.9.5 ? ... yes (2.17.1)
Git user has default SSH configuration? ... yes
Active users: ... 1
Elasticsearch version 5.1 - 5.5? ... no (5.6.9)
For more information see:
doc/integration/elasticsearch.md
Checking GitLab ... Finished

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)