[QA] desktop client sees OCP\LOCK\LockedException when logging in early
Open
Nobody has claimed this yet.
Type:Bug
- Dominant language
- PHP
- Stars
- 8.8k
- Forks
- 2.1k
- Avg merge
- 20h 7m
- Merged PRs (30d)
- 41
Description
- docker run -v 8080:8080 owncloud/server:10.6.0-rc2
- login with a 2.7.3 desktop client to that server immediately after it is up
- a strange 503 error appears:
but that does not prevent login. Everything works fine.
Expected behaviour: Server unvailable should be what it says, or not shown at all.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with owncloud/server:10.6.0-rc2 and a 2.7.3 desktop client by logging in immediately after the server starts. Trace the server-side login response that produces the OCP\LOCK\LockedException and compare it with the expected unavailable-server behavior; done when the misleading 503 no longer appears or accurately reports availability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- api, backend, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100