CI cannot clone non-public submodule
Summary
The CI cannot clone a non-public submodule. It looks like the ci-token doesn't give the job permission to clone using ssh. It works if I include the submodule with https.
Steps to reproduce
- Add this specific non-public repository as a submodule
- Run the CI
I'm working on gitlab.cern.ch, this problem doesn't seem to happen all the time, but it keeps happening with this specific repository. I checked that the repository is configured correctly to be accessible via CI from the other repository.
Actual behavior
Cloning into '/home/gitlab-runner/builds/5JeAKmCkD/2/atlas-tdaq-p2-firmware/global-trigger/gep-fw/ipbus'...
remote: The project you were looking for could not be found or you don't have permission to view it.
fatal: repository 'https://gitlab.cern.ch/atlas-tdaq-p2-firmware/tdaq_shared_firmware/ipbus-firmware/' not found
fatal: clone of 'https://gitlab-ci-token:[MASKED]@gitlab.cern.ch/atlas-tdaq-p2-firmware/tdaq_shared_firmware/ipbus-firmware' into submodule path '/home/gitlab-runner/builds/5JeAKmCkD/2/atlas-tdaq-p2-firmware/global-trigger/gep-fw/ipbus' failed
Failed to clone 'ipbus'. Retry scheduled
Expected behavior
Cloning into '/home/gitlab-runner/builds/pkRY8V3t/2/atlas-tdaq-p2-firmware/global-trigger/gep-fw/Hog'...
warning: redirecting to https://gitlab.cern.ch/hog/Hog.git/
Cloning into '/home/gitlab-runner/builds/pkRY8V3t/2/atlas-tdaq-p2-firmware/global-trigger/gep-fw/core1990'...
Cloning into '/home/gitlab-runner/builds/pkRY8V3t/2/atlas-tdaq-p2-firmware/global-trigger/gep-fw/ipbus'...
warning: redirecting to https://gitlab.cern.ch/atlas-tdaq-p2-firmware/ipbus-firmware.git/
Submodule path 'Hog': checked out '20623bf3fd23300d471bb2ac791bbee2229aa9fa'
Submodule path 'core1990': checked out '6d4a116ac1ddbf448a1652a426a02aaf193af2e2'
Submodule path 'ipbus': checked out '21ec06e5c2e957856b990d346651450f58cb362a'
Entering 'Hog'
Entering 'core1990'
Entering 'ipbus'
Environment description
I'm using runner on a CERN handled VM, no containers, just shell. Exactly the same CI used to work, this might be linked with a recent upgrade to Alma9 on the VMs