Packages registry responds with 404 and no package get created

Summary

Generic packages registry doesn't save packages.

IMPORTANT: Using a CI flow that has worked for almost a year now, without any recent change on our end.

Steps to reproduce

uploading a packages give us the correct 201 response.

doing:

curl -s --header "JOB-TOKEN: $CI_JOB_TOKEN" --upload-file .package/${THE_PACKAGE} "${PACKAGES_URL}/${THE_PACKAGE_VERSION}/${THE_PACKAGE}"

results:

{"message":"201 Created"}

Example Project

I have real-life projects I can show to gitlab staff directly

What is the current bug behavior?

when navigating to packages registry listing the newly created package is not there. When trying to download the package using API, it responds with 404

What is the expected correct behavior?

both of the above should work OK

Relevant logs and/or screenshots

  TASK [app-build : DEBUG: Try getting the package using the master branch] ***
    fatal: [localhost]: FAILED! => changed=false
      dest: /tmp/app_build/
      elapsed: 0
      gid: 0
      group: root
      mode: '0755'
      msg: Request failed
      owner: root
      response: 'HTTP Error 404: Not Found'
      size: 4096
      state: directory
      status_code: 404
      uid: 0
      url: ***redacted***