Skip to content
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.

Sign up for GitHub

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

Jump to bottom

OCM. 500 error when federated user uploads files to shared folder #10489

Closed
ScharfViktor opened this issue Nov 6, 2024 · 1 comment
Closed

OCM. 500 error when federated user uploads files to shared folder #10489

ScharfViktor opened this issue Nov 6, 2024 · 1 comment
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug

Comments

@ScharfViktor
Copy link
Contributor

ocis: 6.6.1+6f3322a3d
web: 11.0.1

setup: https://github.com/owncloud/web/blob/master/docker-compose.yml or https://owncloud.dev/ocis/development/testing/#running-test-suite-with-federated-sharing-ocm
Steps:

  • 2 users create connection
  • user1 creates folder f2 and shares to user2 with edit role
  • user2 tries to create new folder inside the shared folder

Actual: new folder is created with /

  • user2 tries to upload files inside the shared folder

Actual: 500 error
image

log:

2024-11-06 13:55:18 2024-11-06T12:55:18Z ERR error doing PATCH request to data service error="Patch \"http://localhost:9280/data/tus/22a772a8-d4c5-4b63-bc69-d76bf1cd669a\": dial tcp 127.0.0.1:9280: connect: connection refused" pkg=rhttp request-id=20dd045fe189/pRaqUU7WIz-001271 service=frontend traceid=13c7e6eff6b32b35fe5ca829cb90eb84
2024-11-06 13:55:18 2024-11-06T12:55:18Z ERR http end="06/Nov/2024:12:55:18 +0000" host=127.0.0.1 method=PATCH pkg=rhttp proto=HTTP/1.1 service=frontend size=0 start="06/Nov/2024:12:55:18 +0000" status=500 time_ns=2053666 traceid=13c7e6eff6b32b35fe5ca829cb90eb84 uri=/data/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNzMwOTg0MTE4LCJpYXQiOjE3MzA4OTc3MTgsInRhcmdldCI6Imh0dHA6Ly9sb2NhbGhvc3Q6OTI4MC9kYXRhL3R1cy8yMmE3NzJhOC1kNGM1LTRiNjMtYmM2OS1kNzZiZjFjZDY2OWEifQ.rWleKyBL6b_JBS8iMgcm3Opdauz-8QMZ8Xq-SgHvOyw url=/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNzMwOTg0MTE4LCJpYXQiOjE3MzA4OTc3MTgsInRhcmdldCI6Imh0dHA6Ly9sb2NhbGhvc3Q6OTI4MC9kYXRhL3R1cy8yMmE3NzJhOC1kNGM1LTRiNjMtYmM2OS1kNzZiZjFjZDY2OWEifQ.rWleKyBL6b_JBS8iMgcm3Opdauz-8QMZ8Xq-SgHvOyw
@ScharfViktor ScharfViktor added Type:Bug Priority:p2-high Escalation, on top of current planning, release blocker labels Nov 6, 2024
@ScharfViktor ScharfViktor moved this from Qualification to Prio 2 in Infinite Scale Team Board Nov 6, 2024
@2403905 2403905 self-assigned this Nov 7, 2024
@ScharfViktor
Copy link
Contributor Author

seems that was fixed 4792071

@2403905 2403905 removed their assignment Nov 8, 2024
@github-project-automation github-project-automation bot moved this from In progress to Done in Infinite Scale Team Board Nov 8, 2024
@ScharfViktor ScharfViktor mentioned this issue Nov 8, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority:p2-high Escalation, on top of current planning, release blocker Type:Bug
Projects
Infinite Scale Team Board
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@2403905 @ScharfViktor