SAST artifacts not accessible in 13.3

Summary

When adding GitLab's SAST template to my build, artifacts are generated and uploaded, but are not accessible. We have not attempted to use this functionality in previous versions, so I'm not sure if it's a regression or not.

Steps to reproduce

I added the following to my .gitlab-ci.yml file:

include:
  - template: Security/SAST.gitlab-ci.yml

sast:
  stage: test
  tags:
    - linux
    - dockrun

Example Project

Unfortunately, we're using CE self-hosted behind a corporate firewall, so I can't link to the project here.

What is the current bug behavior?

Artifact is detected and uploaded, but no buttons show in the job's page.

What is the expected correct behavior?

Based on the documentation, I expect buttons like Browse and Download to be available.

Relevant logs and/or screenshots

Screen_Shot_2020-08-25_at_9.28.46_AM

On the right, the Job artifacts section is shown with the expiration information, but no controls are available to view or download the artifacts.

At the bottom, the report file is detected and is reported to have uploaded successfully.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
System information
System:         Ubuntu 16.04
Current User:   git
Using RVM:      no
Ruby Version:   2.6.6p146
Gem Version:    2.7.10
Bundler Version:1.17.3
Rake Version:   12.3.3
Redis Version:  5.0.9
Git Version:    2.28.0
Sidekiq Version:5.2.9
Go Version:     unknown

GitLab information
Version:        13.3.0
Revision:       9119206b6e8
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     11.7
URL:            https://gitlab.rticonnect.net
HTTP Clone URL: https://gitlab.rticonnect.net/some-group/some-project.git
SSH Clone URL:  git@gitlab.rticonnect.net:some-group/some-project.git
Using LDAP:     yes
Using Omniauth: yes
Omniauth Providers: 

GitLab Shell
Version:        13.6.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 
Checking GitLab subtasks ...


Checking GitLab Shell ...


GitLab Shell: ... GitLab Shell version >= 13.6.0 ? ... OK (13.6.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 ... 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: ... Server: ldapmain

LDAP authentication... Success

LDAP users with access to your GitLab server (only showing the first 100 results)
User output sanitized. Found 100 users of 100 limit.


Checking LDAP ... Finished


Checking GitLab App ...


Git configured correctly? ... yes
Database config exists? ... yes                                                                                                                                                                                                [62/1889]
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: ...
3/1 ... yes
3/3 ... yes
1/5 ... yes
3/6 ... yes
3/7 ... yes
6/9 ... yes
6/10 ... yes
3/11 ... yes
3/12 ... yes
3/13 ... yes
6/14 ... yes
3/16 ... yes
3/17 ... yes
3/19 ... yes
11/22 ... yes
12/23 ... yes
3/24 ... yes
3/28 ... yes
6/29 ... yes
3/30 ... yes
1/31 ... yes
3/33 ... yes
3/35 ... yes
3/36 ... yes
3/38 ... yes
3/39 ... yes
3/40 ... yes
3/41 ... yes
3/42 ... yes
3/43 ... yes
3/44 ... yes
3/45 ... yes
3/46 ... yes
3/47 ... yes
3/48 ... yes
21/49 ... yes
30/52 ... yes
3/55 ... yes
5/56 ... yes
38/57 ... yes
38/58 ... yes
38/59 ... yes
3/60 ... yes
3/61 ... yes
38/62 ... yes
12/63 ... yes
14/65 ... yes
5/66 ... yes
12/67 ... yes
3/68 ... yes
5/70 ... yes
2/73 ... yes
3/74 ... yes
15/75 ... yes
15/76 ... yes
5/77 ... yes
15/78 ... yes
15/79 ... yes
15/80 ... yes
6/81 ... yes
3/82 ... yes
2/83 ... yes
2/84 ... yes
2/85 ... yes
3/86 ... yes
3/88 ... yes
3/89 ... yes
3/90 ... yes
3/91 ... yes
3/92 ... yes
3/93 ... yes
3/94 ... yes
5/95 ... yes
2/96 ... yes
12/97 ... yes
40/98 ... yes
3/99 ... yes
2/100 ... yes
3/101 ... yes
3/102 ... yes
7/104 ... yes
7/105 ... yes
60/106 ... yes
3/107 ... yes
2/108 ... yes
12/110 ... yes
15/111 ... yes
3/112 ... yes
15/113 ... yes
3/114 ... yes
3/115 ... yes
2/116 ... yes
6/117 ... yes
6/118 ... yes
Redis version >= 4.0.0? ... yes
Ruby version >= 2.5.3 ? ... yes (2.6.6)
Git version >= 2.24.0 ? ... yes (2.28.0)
Git user has default SSH configuration? ... yes
Active users: ... 40
Is authorized keys file accessible? ... yes
GitLab configured to store new projects in hashed storage? ... yes
All projects are in hashed storage? ... no
Try fixing it:
Please migrate all projects to hashed storage
as legacy storage is deprecated in 13.0 and support will be removed in 14.0.
For more information see:
doc/administration/repository_storage_types.md


Checking GitLab App ... Finished


Checking GitLab subtasks ... Finished

Possible fixes

Unfortunately, I am not aware of any fixes or workarounds for this issue.

Edited by John Plaxco