Upload a package file regression
Summary
Since 14.6 no response when uploading artifact to package registry.
Steps to reproduce
Upload artifact to package registry https://docs.gitlab.com/ee/api/packages/maven.html#upload-a-package-file
curl --request PUT \
--upload-file path/to/mypkg-1.0-SNAPSHOT.pom \
--header "Private-Token: <personal_access_token>" \
"https://gitlab.example.com/api/v4/projects/1/packages/maven/foo/bar/mypkg/1.0-SNAPSHOT/mypkg-1.0-SNAPSHOT.pom"
Before 14.6, response contains json with file_sha1
and updated_at
. Now, response is null.
Example Project
What is the current bug behavior?
Regression, response is null.
What is the expected correct behavior?
A json response with file_sha1
and updated_at
attributes.
Relevant logs and/or screenshots
Output of checks
Sample of previous response :
{"id":86865,"package_id":8041,"created_at":"2021-03-12T16:29:49.768Z","updated_at":"2021-03-12T16:29:49.768Z","size":200857,"file_store":2,"file_md5":"38f774e5f5d0179922d12b25787bf9ba",
"file_sha1":"b0d09c01f1229c3f390b63335808c13e33eb5b9b","file_name":"commons-io-2.8.jar","file":{"url":"https://krp2pfkistgbluereg.blob....zsTyO1oQAYFAeH9tITKxAM2p2wIVvKE2M9VPw%3D"},
"verification_retry_at":null,"verified_at":null,"verification_failure":null,"verification_retry_count":null,"file_sha256":null,"verification_checksum":null,"verification_state":0,"verification_started_at":null}
Actual response : null
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`) (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
)(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
Edited by JF