Merge pull request github#30842 from github/repo-sync

Repo sync
ebfork · Dec 27, 2023 · 283b435 · 283b435
2 parents c0fe7a2 + 6857e42
commit 283b435
Show file tree

Hide file tree

Showing 3 changed files with 46 additions and 0 deletions.
diff --git a/data/release-notes/enterprise-server/3-11/1.yml b/data/release-notes/enterprise-server/3-11/1.yml
@@ -1,4 +1,10 @@
 date: '2023-12-21'
+intro: |
+  {% warning %}
+  
+  **Warning**: Hotpatch upgrades from GitHub Enterprise Server version `3.11.0` to `3.11.1` will result in the instance losing network connectivity after a reboot. We have removed the hotpatch upgrade package for the `3.11.1` version of GitHub Enterprise Server to ensure this upgrade path is not executed accidentally. Before you upgrade, please make sure you have read the "[Known issues](#3.11.1-known-issues)" section of these release notes.
+      
+  {% endwarning %}
 sections:
   security_fixes:
     - |
@@ -74,6 +80,8 @@ sections:
     - |
       On an instance in a cluster configuration, administrators can identify the repository networks or gists that are common across a specified set of storage nodes using the `spokesctl find-on-replicas` command.
   known_issues:
+    - |
+      {% data reusables.release-notes.2023-12-networking-issue-in-ghes-3-11-1 %} [Updated 2023-12-27]
     - |
       Custom firewall rules are removed during the upgrade process.
     - |

diff --git a/data/release-notes/enterprise-server/3-11/2.yml b/data/release-notes/enterprise-server/3-11/2.yml
@@ -0,0 +1,35 @@
+date: '2023-12-27'
+sections:
+  bugs:
+    - When an instance is upgraded with a hotpatch, the instance may lose network connectivity after a reboot.
+  known_issues:
+    - |
+      An upgrade to GitHub Enterprise Server 3.11 may fail, hanging on the "Reloading system services" screen. The following error will appear in `/var/log/syslog`.
+
+      ```text
+      agent: Error starting agent: error="Failed to start Consul server: Failed to start Raft: failed to load any existing snapshots"
+      ```
+
+      To address this issue, [contact GitHub Support](https://support.github.com/contact).
+    - |
+      Custom firewall rules are removed during the upgrade process.
+    - |
+      During the validation phase of a configuration run, a `No such object` error may occur for the Notebook and Viewscreen services. This error can be ignored as the services should still correctly start.
+    - |
+      If the root site administrator is locked out of the Management Console after failed login attempts, the account does not unlock automatically after the defined lockout time. Someone with administrative SSH access to the instance must unlock the account using the administrative shell. For more information, see "[AUTOTITLE](/admin/configuration/administering-your-instance-from-the-management-console/troubleshooting-access-to-the-management-console#unlocking-the-root-site-administrator-account)."
+    - |
+      If an instance is configured to forward logs to a target server with TLS enabled, certificate authority (CA) bundles that a site administrator uploads using `ghe-ssl-ca-certificate-install` are not respected, and connections to the server fail.
+    - |
+      The `mbind: Operation not permitted` error in the `/var/log/mysql/mysql.err` file can be ignored. MySQL 8 does not gracefully handle when the `CAP_SYS_NICE` capability isn't required, and outputs an error instead of a warning.
+    - |
+      On an instance hosted in AWS, system time may lose synchronization with Amazon's servers after an administrator reboots the instance.
+    - |
+      On an instance with the HTTP `X-Forwarded-For` header configured for use behind a load balancer, all client IP addresses in the instance's audit log erroneously appear as 127.0.0.1.
+    - |
+      {% data reusables.release-notes.2023-10-git-push-made-but-not-registered %}
+    - |
+      {% data reusables.release-notes.large-adoc-files-issue %}
+    - |
+      {% data reusables.release-notes.2023-11-cluster-ha-failover-git-push-failure %}
+    - |
+      Restoring backups with `ghe-restore` on a GHES cluster will exit prematurely if `redis` has not restarted properly.
diff --git a/data/reusables/release-notes/2023-12-networking-issue-in-ghes-3-11-1.md b/data/reusables/release-notes/2023-12-networking-issue-in-ghes-3-11-1.md
@@ -0,0 +1,3 @@
+[Hotpatch upgrades](/admin/monitoring-managing-and-updating-your-instance/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server#upgrading-with-a-hotpatch) from GitHub Enterprise Server version `3.11.0` to `3.11.1` will result in the appliance losing network connectivity after a reboot.
+If you have upgraded to GitHub Enterprise Server `3.11.1` from `3.11.0` using a hotpatch upgrade, please contact [GitHub Support](https://support.github.com/) for assistance.
+If you have upgraded directly to GitHub Enterprise Server `3.11.1` from previous versions (for example, from any version of GitHub Enterprise Server in the 3.9 or 3.10 series), your instance is not affected by this issue.