get
/list
/import
: not working with company github + webdavs storage
#8016
Labels
fs: webdav
Related to the Webdav filesystem
Bug Report
get
/list
/import
: not working with (company) github + webdavs storage.See also the discussion here.
Description
I'm trying to import data from a data registry. URL:
[email protected]:company/data-registry.git
. The data-registry stores its data on a webdavs accessible remote server (URL:webdavs://company.com/webdav/data-registry-storage
). To access this server I have created (using the dvc command) a.dvc/config.local
file containing the username and password. I've added the data withdvc add
and pushed it to the remote server.In a second repo, the repo I want to do my experiments, I want to import my a dataset from the data-registry. It's a folder so and I want to put in inside
data/
dvc import [email protected]:company/data-registry.git dataset -o data
I have added the exact same
config
andconfig.local
in this second repo, but I'm getting the following errorFirst the warning is interesting, but maybe a consequence of the error, because the following path does exist on the remote storage
/21/8ff9c6f73767c8126b66f7213cd0d2.dir'
Secondly, I know I am authorized it's how I got the data on the remote in the first place.
Interestingly when I
get
/list
/import
the data by just linking to the local repo it does work.Reproduce
Folder structure:
repos/repo1
,repos/repo2
.Repo 1 (Data registry)
Repo 2 (Experiments)
Fails: With the error in the description (Unauthorized 401)
FYI
218ff9c6f73767c8126b66f7213cd0d2.dir
is the md5 hash in the dataset.dvcWorks:
Same hold for
get
andlist
. Possibly others?Expected
Expected to not make a difference and both methods (local and remote git) to import the data.
Environment information
Output of
dvc doctor
:Additional Information (if any):
Please ask and I can edit/add.
EDIT
When using
dvc status
anddvc pull
the error message is not very informative when the credentials are missing. I cloned a new data registry repo (repo 1 above) and tried to download the data usingdvc pull
which failed and then checkeddvc status --cloud
. It's interesting that these commands do not fail with an "unauthorized error". The commands work fine after addingconfig.local
again.The text was updated successfully, but these errors were encountered: