From d4c43db0b0ad5b45b89c9c214ef2b79cf812f2d9 Mon Sep 17 00:00:00 2001
From: docs-bot <77750099+docs-bot@users.noreply.github.com>
Date: Mon, 26 Aug 2024 07:39:37 -0700
Subject: [PATCH 1/2] [Early access companion] PR #345 (#52097)


From 34cc5a65678a9809e7db96a639b1b613d84f132f Mon Sep 17 00:00:00 2001
From: Donal Ellis <donal@github.com>
Date: Tue, 27 Aug 2024 00:59:02 +1000
Subject: [PATCH 2/2] add known issue for resolvconf failing to start (#52100)

---
 .../release-notes/enterprise-server/3-11/14.yml |   4 ++++
 data/release-notes/enterprise-server/3-12/8.yml |   4 ++++
 data/release-notes/enterprise-server/3-13/3.yml |   4 ++++
 .../.2024-08-resolvconf-wont-start.md.swp       | Bin 0 -> 12288 bytes
 .../2024-08-resolvconf-wont-start.md            |  16 ++++++++++++++++
 5 files changed, 28 insertions(+)
 create mode 100644 data/reusables/release-notes/.2024-08-resolvconf-wont-start.md.swp
 create mode 100644 data/reusables/release-notes/2024-08-resolvconf-wont-start.md

diff --git a/data/release-notes/enterprise-server/3-11/14.yml b/data/release-notes/enterprise-server/3-11/14.yml
index 51b639d76a2c..c738cc36025e 100644
--- a/data/release-notes/enterprise-server/3-11/14.yml
+++ b/data/release-notes/enterprise-server/3-11/14.yml
@@ -101,3 +101,7 @@ sections:
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
     - |
       Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
+    - |
+      {% data reusables.release-notes.2024-08-resolvconf-wont-start %}
+
+      [Updated: 2024-08-26]
diff --git a/data/release-notes/enterprise-server/3-12/8.yml b/data/release-notes/enterprise-server/3-12/8.yml
index 9d3ca60503e5..d3683b583e77 100644
--- a/data/release-notes/enterprise-server/3-12/8.yml
+++ b/data/release-notes/enterprise-server/3-12/8.yml
@@ -109,3 +109,7 @@ sections:
       When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
     - |
       Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
+    - |
+      {% data reusables.release-notes.2024-08-resolvconf-wont-start %}
+
+      [Updated: 2024-08-26]
diff --git a/data/release-notes/enterprise-server/3-13/3.yml b/data/release-notes/enterprise-server/3-13/3.yml
index 354bdb8c310c..621d65e59034 100644
--- a/data/release-notes/enterprise-server/3-13/3.yml
+++ b/data/release-notes/enterprise-server/3-13/3.yml
@@ -123,3 +123,7 @@ sections:
       Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
     - |
       Instance setup in AWS with IMDSv2 enforced fails if no public IP is present.
+    - |
+      {% data reusables.release-notes.2024-08-resolvconf-wont-start %}
+
+      [Updated: 2024-08-26]
diff --git a/data/reusables/release-notes/.2024-08-resolvconf-wont-start.md.swp b/data/reusables/release-notes/.2024-08-resolvconf-wont-start.md.swp
new file mode 100644
index 0000000000000000000000000000000000000000..ad1d97a73f968d158689971dc4ade1f4526c9de4
GIT binary patch
literal 12288
zcmeI2zit#U5XK$)5CktUKygj>_7W(<Nl0msNWtHTG%V73?b*B4`RtYL%_R-tAt)$#
z0$u^p(eMh;QBgp_8!)?fr;E~rlu^dgr#*W;V}HMOv$s<W4)&hFgZ`GFc0-6?2j9w1
zpHFrtUxm=lO4E*?(<W6IpEISq{kBV(j;c6ric~ullFCN(v`VUFl&Qxi$iiTtUj}8s
z#JWhm?ZNi_WU!NX49*-XXUk;fY)nFwKK7^je-`ICOyDXLXkwY{tc!cwTZ0zE-8;A8
z*3DN}nFxDl0!)AjFaajO1egF5U;<Z;K&;oq3Aw(ua87>#bZza-b<yPu6JP>NfC(@G
zCcp%k025#WOn?b60VZ$>2}t^QzPm2O2U7d}fBF9Zazlt0q{pPc*M;~)`b}~qOG45<
zX@m5GV!xBVkUo;ST$hjqZ<z@&0Vco%m;e)C0!)AjFaahYM4sm&G}=Kp4iTp+8t7_|
zVO5a~XD4WhQ)j7W**JOe_=`svIK3jh)}<I#I^VEfT&b>lSwY<o=npG}eVrPor0KV1
z)uNYXulMISvNx%OM@Ojk+bZkl9<zs8T2wYmrxRUy$dVee)HgJ+%G!f$!2vZSRlkrE
z8X+@bjD~8-_ezN4Du7d}@nI8Y&QGLwjn(t<Duf1MMit`JM<|^!ZdTb5C^wx-s{{Oe
z_kKQAjinv6bB%!-eW*eNXX%L)&P7UHG!dwL9GZIMrN%IvKgQNV8eOBtLr~JTGrAu1
zS}&)pq_qpNb{2Kg)Ks31y&*iM6F`wrRtCX&AP%Ua^T($wKC{s7V6!ujuh8VMAP!S`
z45h3LExb5J1uEGDoQIs*N4{DGw8PMu!lTyiY>c*xS!R}zPG=oMn>p`n<sj#~C7d1!
M_!2F8@BC2w1H=MI8UO$Q

literal 0
HcmV?d00001

diff --git a/data/reusables/release-notes/2024-08-resolvconf-wont-start.md b/data/reusables/release-notes/2024-08-resolvconf-wont-start.md
new file mode 100644
index 000000000000..5b8a6540e1d0
--- /dev/null
+++ b/data/reusables/release-notes/2024-08-resolvconf-wont-start.md
@@ -0,0 +1,16 @@
+On boot, the `resolvconf` service may fail to start because the `/run/resolvconf` directory does not exist when the service attempts to `touch` a file there, with the error:
+
+```shell
+/bin/touch: cannot touch '/run/resolvconf/postponed-update': No such file or directory
+```
+
+If this occurs, workaround this issue with the following commands — this change will persist on reboots, but not upgrades:
+
+```shell
+sudo sed -i.bak \
+'/\[Service\]/a ExecStartPre\=\/bin\/mkdir \-p \/run\/resolvconf' \
+/etc/systemd/system/resolvconf.service.d/local.conf
+
+sudo systemctl daemon-reload
+sudo systemctl start resolvconf 
+```