-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
exp push: unexpected http resp 403 with gitlab CI from ec2 instance #9981
Comments
Just to clarify, the issue here is pushing the experiment commit to the gitlab git server, not with pushing DVC cache to S3 |
Does the token you use have the correct scope to push to the repo? See https://stackoverflow.com/a/73394648/3127500 for example. |
The token does have write repository permissions. I don't explicitly config the git remote like in the SO answer you've linked. I am able to use |
Also, I was able to push experiments in the past with the same project access token and an older version of DVC |
For the sake of completeness, do you mind checking if using |
It looks like running |
Bug Report
Description
I have an EC2 instance which runs a cml runner. The cml runner picks up a gitlab ci job which pulls data, runs experiments, and pushes experiments. The data is being pulled properly and I can run
dvc push
with no errors. I have verified thataws cli
commands work just fine on the EC2 instance, but I am unable toexp push
. When I rundvc exp push origin --run-cache -vv
I am getting the following output:Reproduce
Expected
Environment information
Output of
dvc doctor
:Additional Information (if any):
It's possible that this is a version incompatibility issue, but I was able to exp push before I was using dvclive with dvc 3.12.0. I can also run everything locally with python 3.10, but upgrading my cloud python version is kind of a pain, it would be easier to downgrade dvc and dependencies. I tried with dvc 3.22 and 3.20, but there was the same issue.
The text was updated successfully, but these errors were encountered: