Bump SwarmKit to 1a0ebd43b2d156983a695f90e56f4ecba6ced902#38520
Bump SwarmKit to 1a0ebd43b2d156983a695f90e56f4ecba6ced902#38520thaJeztah merged 2 commits intomoby:masterfrom
Conversation
|
Let's see if this works; updated the vendored code in this PR just to give it a quick try 😅 |
ad96b5a to
b3b739a
Compare
Codecov Report
@@ Coverage Diff @@
## master #38520 +/- ##
=========================================
Coverage ? 36.6%
=========================================
Files ? 610
Lines ? 45233
Branches ? 0
=========================================
Hits ? 16558
Misses ? 26392
Partials ? 2283 |
b3b739a to
cf9f75e
Compare
|
Tested with my new tool #38523 works (renamed test to trigger test). Passed nicely all 25 tries. Log from that test: 38520_test-integration-flaky.log Looks good 👍 |
|
Opened an upstream PR in SwarmKit; moby/swarmkit#2804 |
Full diff: moby/swarmkit@8af8c42...1a0ebd4 relevant changes: - swarmkit#2771 Allow using Configs as CredentialSpecs - swarmkit#2804 Make Service.UpdateStatus non-ambiguous - swarmkit#2805 Refactor condition in restart supervisor - swarmkit#2780 api: add BindOptions.NonRecursive - related to moby#38003 - swarmkit#2790 Fix possible panic if NetworkConfig is nil - swarmkit#2797 Include old error-message for backward compatibility - related to swarmkit#2779 / moby#38140 / moby#38142 Signed-off-by: Sebastiaan van Stijn <[email protected]>
It's no longer needed with the latest swarmkit changes Signed-off-by: Sebastiaan van Stijn <[email protected]>
cf9f75e to
94429d4
Compare
|
Ping @dperny - guess we need an updated description in the API reference for ping @AkihiroSuda this brings in moby/swarmkit#2780 (did you prepare changes already for |
I can open follow-up PR |
|
All green |
moby/swarmkit@8af8c42...1a0ebd4
relevant changes:
See description below for the original PR description (before swarmkit bump)
In situations where only annotations of a service were updated, SwarmKit never marks a service as
UpdateStateUpdating; the service'sUpdateStatusis set tonil, and never updated after.Because of this, it's not possible to verify if the update actually happened (unless comparing the services
Versionbefore and after).This patch modifies the SwarmKit vendored code to try to make this situation non-ambigious, and mark the services as "updated" in all cases.
Relates to #38499 (comment) :