-
Notifications
You must be signed in to change notification settings - Fork 186
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
[QA] Upload to ocis-1.0.0-rc6 on eos fails #997
Comments
Also reproduced locally with
|
The last lines show the problem:
The WRN in the middle can be ignored. There is always a stat request to check if the file exists because webdav requires different http response codes. Need to dig into the |
Hm, seems the data provider url is empty... Wtf... Likely a config issue... Need to check the env vars... |
@jnweiger what is the content of |
the It cannot be the one from the datagateway, because we would see a target log line from https://github.com/cs3org/reva/blob/86b255003b34533f99e34d5f765c6245b41526f0/internal/http/services/datagateway/datagateway.go#L219 so our which brings me to this recently introduced for loop: https://github.com/cs3org/reva/blame/b8759471f079f231c8a5a48797fdba771cd1729f/internal/http/services/owncloud/ocdav/tus.go#L171-L177 which is part of a PR that refactors the upload: cs3org/reva#1321 @ishank011 something broke there |
ok ... tus has been deliberately disabled for eos ... https://github.com/cs3org/reva/pull/1321/files#diff-360b3e8fed176d54eac93c1c3671153bb1516cb66b0debb4c2885c271e5296d9R78-R80 @ishank011 @labkode can you elaborate what is not working with tus? AFAICT we should be able to map the existing upload mechanisms to it. Data transfers package #1321 does not mention reasons. I found Enable different data transfer protocolos #1266, which talks about maturity. (TUS as a protocol is mature ... I was under the impression that we wanted to get rid of having to store chunks on the frontend servers before sending them to eos). Maybe clarify in Review EOS TUS implementation and understand interplay with tusd lib interfaces #703 |
The capabilities contain
Server started with
has
It does not seem to make a difference for me. |
@jnweiger setting the env is not good enough. the STORAGE_FRONTEND_UPLOAD_DISABLE_TUS=true needs to either be set in the docker-compose-eos-test.yml under |
I am trying to cover all of the known environmenty places. Except for
Anything else? It is insane already, but still has no effect. |
@butonic @jnweiger for the reva version you're using, setting this env variable should be good enough. But in a recent commit cs3org/reva#1331, I modified the boolean capabilities parameter to a string one using which we can specify the chunking protocol https://github.com/cs3org/reva/blob/master/internal/http/services/owncloud/ocs/config/config.go#L32. The default value is |
@butonic oops, are we using an old reva version? |
Workaround: start the client with |
Michael Barz commented: We need to clarify TUS with EOS storage with @labkode |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 10 days if no further activity occurs. Thank you for your contributions. |
Deployed ocis-1.0.0-rc6 via hetzner-deploy/make_ocis_eos_compose_test.sh
Upload via web interface fails with
Upload via desktop client fails with
12/1/20 3:09:31 PM, stay_home_mainpost.de_Sven_Hoppe.jpg, testpilotcloud5,Server replied "500 Internal Server Error" to "POST https://168.119.152.147:9200/remote.php/dav/files/richard/" (skipped due to earlier error, trying again in 11 second(s))
12/1/20 3:08:01 PM, README.md, testpilotcloud3,Server replied "500 Internal Server Error" to "POST https://ocis-1-0-0-rc6-eos.jw-qa.owncloud.works:9200/remote.php/dav/files/einstein/"
serve rlog snippet:
The text was updated successfully, but these errors were encountered: