-
Notifications
You must be signed in to change notification settings - Fork 1.2k
dvc push
doesn't update cloud info with cloud versioned remotes
#9947
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
Comments
Yes, they are tied to the remote name defined in that git commit's
We should be pushing the file to the I'm guessing this is an index bug caused by both remotes using the same s3 bucket. It looks like the user from the original discussion/context is using dvc==3.0.0 so this may just be a duplicate of #9904 (which is fixed in the latest release) |
@pmrowla I think I was able to reproduce it on the recent DVC version. |
I can also reproduce this with a single remote by changing the remote path. DVC will update the remote name but won't notice that it needs to push again. It seems like DVC isn't checking whether the version IDs actually exist. I remember discussing this in #8766 but I think @pmrowla rightly saw it as dangerous and we continued to check which version were available. |
Context: #9907 (reply in thread)
Let's say we have two remotes:
Let's say we need to migrate data from one to another.
I would expect commands like this:
to work and update
.dvc
\dvc.lock
files with an appropriate info, in reality I'm getting:(only remote name is updated, info stays the same, which is wrong for that remote).
In the original issue, even the object is not pushed to the new remote.
Also, in case of cloud versioning I think
prod
/dev
don't make much sense in.dvc
\dvc.lock
. Version_id is unique (I assume) and can't repeat in a different location. I guess we need to use some hash, or location itself in this case. How do we use these names at all? do we expect that specific remote name to exist in a config?The text was updated successfully, but these errors were encountered: