-
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
DVC pull broken after upgrading pipeline from v1 to v2 #5656
Comments
Can you add |
Run dvc pull -v src/server/assets
|
Note the pull is actually not working on MacOS either, it was using cache. On a fresh repo DVC pull results in the same issue:
I have a feeling our remote is screwed up. We are going to rip the bandaid off and create a new remote, rerun everything and add. Will update here. |
Setting up a completely new remote has fixed the issue. I expect there are compatibility issues with v1 and v2 remotes. It's a bit painful to re-upload everything and lose pipeline history, but for the time being this fix works. |
Closing as stale |
Bug Report
Issue name
pull: looks in nonexistent location
Description
We use dvc pull in a Github action, which runs on Azure Linux (labelled Ubuntu in Github actions). Until today that has worked fine. We recently upgraded our pipeline from v1.11 to v2.0.6. On MacOS, everything works as expected with dvc push and dvc pull. On Azure Linux, dvc pull 404s on any files it tries to pull:
This is repeated for all files. Looking at S3, the location DVC is looking in
my-dvc/fa/f8906fa071e94f623456243e5aed63
does not exist. However, locally on MacOS,.dvc/cache/fa/f8906fa071e94f623456243e5aed63
does exist.Reproduce
dvc add file && dvc push file
dvc pull file
Note that I can delete the file on MacOS and run a
dvc pull
successfully.Expected
DVC pull on Linux looks in the same storage location as on MacOS.
Environment information
MacOS
Linux
The missing cache is expected, it is created when running dvc pull.
What I've tried
I have made sure to delete all files and then add them all back, push and pull using exclusively v2.
I have also tried downgrading the entire pipeline to v1, deleting all files and then adding them all back, push and pulling using exclusively v1. The issue persists, so now we can't even roll back!
I have tried resetting index with
rm -rf .dvc/tmp/index
and rerunning pushes.I believe this issue is related: #4343
The text was updated successfully, but these errors were encountered: