-
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
pull: The specified blob does not exist #9730
Comments
@rlleshi Could you run |
@efiop ty for the quick response.
|
Closing this as duplicate of #9651 This should be resolved in the latest DVC release (3.14.0 or later). After updating please remove the
If you still see this issue after updating and clearing the site cache feel free to re-open this ticket. |
Bug Report
Description
I am pushing the files with
dvc push
to an Azure blob. I then try todvc pull
the files from another machine/repo using the exact samedvc.lock
and authentication method to Azure. Now I get:If I try previous versions of the
dvc.lock
in this other machine/repo, it will work as expected. The latest version just fails.I think the files are being pushed correctly because if I revert to a previous version of the
dvc.lock
file on my local machine (the one where I originally pushed the data) and do pull on that, I will get the old version of the data, and if I then go back to the current version, the new version of the data will be pulled and replaces the old one.So this error message is super confusing because it seems like the data has been pushed in the remote.
So to sum up:
dvc.lock
is the same3.5.1
but didn't make a diff)But
dvc pull
doesn't work as expected.Environment information
The text was updated successfully, but these errors were encountered: