Rolling update causes "out of sequence" errors for the client.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3.7k
- Forks
- 676
- Avg merge
- 4d 9h
- Merged PRs (30d)
- 6
Description
Rolling update internally changes properties for the service, causing the version to increment. This means that user can randomly get "out of sequence" errors. The solution should be to have a separate version for the spec part only so that it only covers all the properties of the service that a user can change.
This issue is causing TestSwarmPublishAdd to fail in Docker CI.
cc @aaronlehmann
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
Start with the TestSwarmPublishAdd failure in Docker CI and trace how rolling updates change service properties and increment the client-visible version. Define the separate spec version against the user-changeable service properties, then verify that rolling updates no longer cause out-of-sequence errors and that TestSwarmPublishAdd passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100