v2.101.7
This commit is contained in:
parent
806993aae7
commit
a96a10abbf
3 changed files with 95 additions and 1 deletions
|
@ -1,3 +1,81 @@
|
|||
- commits:
|
||||
- subject: Update layers/meta-balena to 61b53fbb8b667de54707cc6aa94fd79674958856
|
||||
hash: 73779a3ef2fb38b63b66a5a20b13b84d4c81f672
|
||||
body: Update layers/meta-balena
|
||||
footer:
|
||||
Changelog-entry: Update layers/meta-balena to 61b53fbb8b667de54707cc6aa94fd79674958856
|
||||
changelog-entry: Update layers/meta-balena to 61b53fbb8b667de54707cc6aa94fd79674958856
|
||||
author: renovate[bot]
|
||||
nested:
|
||||
- commits:
|
||||
- subject: Add automated tests for the Engine healthcheck
|
||||
hash: 16d8dbe0e1dae47b161680a227213247ea699f1a
|
||||
body: ""
|
||||
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: []
|
||||
- subject: Use a lightweight Engine healthcheck
|
||||
hash: 7146e4614c2658d6f7d5384602eb8ad213e08759
|
||||
body: >
|
||||
Previously, our healthcheck verified if we were able to start a
|
||||
new
|
||||
|
||||
container. This had two downsides:
|
||||
|
||||
|
||||
1. It was relatively heavyweight. In devices under heavy load, it would
|
||||
sometimes take so long to run that the Engine was killed by the
|
||||
watchdog.
|
||||
2. It wrote to the storage media. Creating a container involves writing
|
||||
some data to persistent storage, therefore the healthcheck was
|
||||
wearing the storage media.
|
||||
|
||||
This new healthcheck simply pings both `balenad` and `containerd`, which
|
||||
|
||||
is much faster than starting a new container and doesn't write to disk.
|
||||
|
||||
The step of pinging `containerd` is important because we have seen at
|
||||
|
||||
least one case in the past in which `balenad` was working but
|
||||
|
||||
`containerd` wasn't.
|
||||
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: []
|
||||
- subject: Make Engine watchdog termination graceful
|
||||
hash: 9e322ee25bf50949880446f4fb85d1d8e864da37
|
||||
body: >
|
||||
With `WatchdogSignal=SIGTERM` systemd will send a SIGTERM and
|
||||
give the
|
||||
|
||||
Engine 90 seconds to gracefully shutdown before sending a SIGKILL. We
|
||||
|
||||
had cases of Engine metadata on disk getting corrupted after the
|
||||
|
||||
watchdog sent it a SIGKILL directly. This change shall minimize this
|
||||
|
||||
issue.
|
||||
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: meta-balena-2.101.7
|
||||
title: "'Improve Engine healthchecks'"
|
||||
date: 2022-08-17T13:45:38.348Z
|
||||
version: 2.101.7
|
||||
title: "'Update layers/meta-balena digest to 61b53fb'"
|
||||
date: 2022-08-19T11:08:14.063Z
|
||||
- commits:
|
||||
- subject: Update contracts to 39a79c43f1b8ab4426d7a9c1cdeb9a9514101061
|
||||
hash: 0337c4316308d777562af7d40bcded1044e634ae
|
||||
|
|
16
CHANGELOG.md
16
CHANGELOG.md
|
@ -1,6 +1,22 @@
|
|||
Change log
|
||||
-----------
|
||||
|
||||
# v2.101.7
|
||||
## (2022-08-19)
|
||||
|
||||
|
||||
<details>
|
||||
<summary> Update layers/meta-balena to 61b53fbb8b667de54707cc6aa94fd79674958856 [renovate[bot]] </summary>
|
||||
|
||||
> ## meta-balena-2.101.7
|
||||
> ### (2022-08-17)
|
||||
>
|
||||
> * Add automated tests for the Engine healthcheck [Leandro Motta Barros]
|
||||
> * Use a lightweight Engine healthcheck [Leandro Motta Barros]
|
||||
> * Make Engine watchdog termination graceful [Leandro Motta Barros]
|
||||
>
|
||||
</details>
|
||||
|
||||
# v2.101.6+rev1
|
||||
## (2022-08-19)
|
||||
|
||||
|
|
2
VERSION
2
VERSION
|
@ -1 +1 @@
|
|||
2.101.6+rev1
|
||||
2.101.7
|
Loading…
Add table
Reference in a new issue