v2.114.22
This commit is contained in:
parent
b2469e1f54
commit
0681216417
3 changed files with 97 additions and 1 deletions
|
@ -1,3 +1,73 @@
|
|||
- commits:
|
||||
- subject: Update layers/meta-balena to ddaac0ccf50d22ac8d0ed6c73022edd40c68b58e
|
||||
hash: 9b53368b0d64f405ca8292d7684bc789326540ee
|
||||
body: Update layers/meta-balena
|
||||
footer:
|
||||
Changelog-entry: Update layers/meta-balena to ddaac0ccf50d22ac8d0ed6c73022edd40c68b58e
|
||||
changelog-entry: Update layers/meta-balena to ddaac0ccf50d22ac8d0ed6c73022edd40c68b58e
|
||||
author: Renovate Bot
|
||||
nested:
|
||||
- commits:
|
||||
- subject: Update balena-engine to v20.10.36
|
||||
hash: 192ab1d65bcfb50495378f0b7a1481827cc1ae10
|
||||
body: |
|
||||
Update balena-engine from 20.10.35 to 20.10.36
|
||||
footer:
|
||||
Change-type: patch
|
||||
change-type: patch
|
||||
author: Renovate Bot
|
||||
nested:
|
||||
- commits:
|
||||
- subject: Further improve resilience of image pulls
|
||||
hash: d864e340bfe050144252db8b0de9c66a3a40fa20
|
||||
body: >
|
||||
Previously, we'd time-out a pull operation after
|
||||
unsuccessfully retrying
|
||||
|
||||
for about 17 minutes (for details see commit
|
||||
|
||||
582487f832c59c2f734a780ab0492833f29002c9). This worked fine in most
|
||||
|
||||
situations, but we have seen at least one case of a particularly
|
||||
|
||||
unreliable network connection that would not be able to finish a large
|
||||
|
||||
pull when operating under this policy.
|
||||
|
||||
|
||||
This commit:
|
||||
|
||||
|
||||
* Completely removes timeouts from image pulls. We'll keep retrying
|
||||
forever, or until users cancel the pull. (From the perspective of the
|
||||
REST API, "canceling" mean closing the HTTP connection. This is what
|
||||
happens when a user Ctrl+C during a pull in the CLI, or, say, we kill
|
||||
a curl process that was using the REST API to pull image.)
|
||||
* Still uses exponential back-off, but we now limit the interval between
|
||||
retries to 5 minutes. The rationale is that some very unreliable
|
||||
networks may be up only for relatively small time windows. Therefore,
|
||||
using intervals that are too long would increase the risk of missing
|
||||
these windows.
|
||||
* Tries to avoid flooding the log stream with messages about retries.
|
||||
We'll log every retry attempt up to the 10th. After that, we'll log
|
||||
retries only once about every 2h. This retry count is reset every time
|
||||
we successfully download any amount of data.
|
||||
footer:
|
||||
Signed-off-by: Leandro Motta Barros <leandro@balena.io>
|
||||
signed-off-by: Leandro Motta Barros <leandro@balena.io>
|
||||
Change-type: patch
|
||||
change-type: patch
|
||||
author: Leandro Motta Barros
|
||||
nested: []
|
||||
version: balena-engine-20.10.36
|
||||
title: ""
|
||||
date: 2023-05-04T10:15:21.705Z
|
||||
version: meta-balena-2.114.22
|
||||
title: ""
|
||||
date: 2023-05-05T07:14:09.662Z
|
||||
version: 2.114.22
|
||||
title: ""
|
||||
date: 2023-05-05T09:14:52.799Z
|
||||
- commits:
|
||||
- subject: Update layers/meta-balena to 0f0fec2a68746d8616cc55a06cf636363786bdca
|
||||
hash: 25095758dcc3d3e10cc92663b204ca1175cbbd64
|
||||
|
|
26
CHANGELOG.md
26
CHANGELOG.md
|
@ -1,6 +1,32 @@
|
|||
Change log
|
||||
-----------
|
||||
|
||||
# v2.114.22
|
||||
## (2023-05-05)
|
||||
|
||||
|
||||
<details>
|
||||
<summary> Update layers/meta-balena to ddaac0ccf50d22ac8d0ed6c73022edd40c68b58e [Renovate Bot] </summary>
|
||||
|
||||
> ## meta-balena-2.114.22
|
||||
> ### (2023-05-05)
|
||||
>
|
||||
>
|
||||
> <details>
|
||||
> <summary> Update balena-engine to v20.10.36 [Renovate Bot] </summary>
|
||||
>
|
||||
>> ### balena-engine-20.10.36
|
||||
>> #### (2023-05-04)
|
||||
>>
|
||||
>> * Further improve resilience of image pulls [Leandro Motta Barros]
|
||||
>>
|
||||
>
|
||||
> </details>
|
||||
>
|
||||
>
|
||||
|
||||
</details>
|
||||
|
||||
# v2.114.21
|
||||
## (2023-05-05)
|
||||
|
||||
|
|
2
VERSION
2
VERSION
|
@ -1 +1 @@
|
|||
2.114.21
|
||||
2.114.22
|
Loading…
Add table
Reference in a new issue