v2.115.5

2023-06-08 12:06:48 +00:00 · 2023-06-08 12:06:48 +00:00 · 05159fde27
commit 05159fde27
parent c85ba9be59
3 changed files with 129 additions and 1 deletions
--- a/.versionbot/CHANGELOG.yml
+++ b/.versionbot/CHANGELOG.yml
@ -1,3 +1,103 @@
+- commits:
+    - subject: Update layers/meta-balena to 7c31e98312e50f7cc6380b00701c6ed8ff3da216
+      hash: 1668a6021da3e4c2ac921f47ecc167ce773798ab
+      body: Update layers/meta-balena
+      footer:
+        Changelog-entry: Update layers/meta-balena to 7c31e98312e50f7cc6380b00701c6ed8ff3da216
+        changelog-entry: Update layers/meta-balena to 7c31e98312e50f7cc6380b00701c6ed8ff3da216
+      author: Self-hosted Renovate Bot
+      nested:
+        - commits:
+            - subject: Update balena-supervisor to v14.11.2
+              hash: e1361fa5dc3f18733cb07b24ad9e6aaa0f5984e4
+              body: |
+                Update balena-supervisor from 14.11.1 to 14.11.2
+              footer:
+                Change-type: patch
+                change-type: patch
+              author: Self-hosted Renovate Bot
+              nested:
+                - commits:
+                    - subject: Handle Engine-host race condition for "always" and "unless-stopped"
+                        restart policy
+                      hash: 7f3214195838a8bf3242ef7540b4487338687e4c
+                      body: >
+                        There exists a race condition between Engine and a host
+                        resource that may not
+
+                        be immediately created. In this race condition, if a container's compose config
+
+                        depends on the existence of that host resource, such as a network interface, and the
+
+                        Engine tries to create & start the container before the host resource is created, the
+
+                        Engine will not reattempt to start the container, regardless of the restart policy.
+
+                        This is undesireable behavior but seems to be the behavior as implemented by Docker.
+
+
+                        To rectify this, the Supervisor state funnel noops for a grace period of 1 minute
+
+                        after starting a container to see that the container's status has become 'running`.
+
+                        If the container exits because of the race condition, the status becomes 'exited' and the
+
+                        Supervisor will attempt to generate another start step. This noop-wait-start step loop
+
+                        will repeat until the container is able to start.
+
+
+                        If the container is never able to start, there was a problem in the host in the creation of the
+
+                        host resource, and that should be fixed at the host level.
+
+
+                        This commit does not handle the case of services with restart policies "no" or "on-failure"
+
+                        which encounter this host race, as metadata from container inspects needs to be introduced
+
+                        during step calculation in order to figure out whether services with those restart policies
+
+                        need to be started. This will be fixed in a future PR.
+                      footer:
+                        Change-type: patch
+                        change-type: patch
+                        Signed-off-by: Christina Ying Wang <christina@balena.io>
+                        signed-off-by: Christina Ying Wang <christina@balena.io>
+                      author: Christina Ying Wang
+                      nested: []
+                  version: balena-supervisor-14.11.2
+                  title: ""
+                  date: 2023-06-05T18:53:18.287Z
+          version: meta-balena-2.115.5
+          title: ""
+          date: 2023-06-08T10:17:55.709Z
+    - subject: Remove pull_request_target event run for ESR targets
+      hash: 5253c25bfac8eb4c429f275c5282677816c59d0a
+      body: >
+        Backporting to ESR branches hits a flowzone error as both pull_request
+
+        and pull_request_target run and this only works for master.
+
+
+        Removing the pull_request_target run for ESR branches fixes this, but
+
+        also removes the possibility of external pull requests into ESR branches,
+
+        which we don't actually need.
+
+
+        [skip ci]
+      footer:
+        Changelog-entry: Remove pull_request_target event run for ESR targets
+        changelog-entry: Remove pull_request_target event run for ESR targets
+        Signed-off-by: Alex Gonzalez <alexg@balena.io>
+        signed-off-by: Alex Gonzalez <alexg@balena.io>
+      author: Alex Gonzalez
+      nested: []
+  version: 2.115.5
+  title: ""
+  date: 2023-06-08T12:06:41.441Z
 - commits:
    - subject: Update balena-os/github-workflows to
      hash: 59c1ae7dc0d1fe81755b9309a0b08e3628dcf8b3
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@ -1,6 +1,34 @@
 Change log
 -----------

+# v2.115.5
+## (2023-06-08)
+
+
+<details>
+<summary> Update layers/meta-balena to 7c31e98312e50f7cc6380b00701c6ed8ff3da216 [Self-hosted Renovate Bot] </summary>
+
+> ## meta-balena-2.115.5
+> ### (2023-06-08)
+> 
+> 
+> <details>
+> <summary> Update balena-supervisor to v14.11.2 [Self-hosted Renovate Bot] </summary>
+> 
+>> ### balena-supervisor-14.11.2
+>> #### (2023-06-05)
+>> 
+>> * Handle Engine-host race condition for "always" and "unless-stopped" restart policy [Christina Ying Wang]
+>> 
+> 
+> </details>
+> 
+> 
+
+</details>
+
+* Remove pull_request_target event run for ESR targets [Alex Gonzalez]
+
 # v2.115.4+rev1
 ## (2023-06-01)

--- a/2
+++ b/2
@ -1 +1 @@
-2.115.4+rev1
+2.115.5