From b57272bd7cab2612bcd781e93b9b9fb96a82e173 Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Tue, 8 Aug 2023 09:50:54 -0400 Subject: [PATCH 1/3] Adding known issue Adding known issue for https://github.com/github/ghes/issues/6954 to 3.9.0 and 3.9.1 --- data/release-notes/enterprise-server/3-9/0.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/data/release-notes/enterprise-server/3-9/0.yml b/data/release-notes/enterprise-server/3-9/0.yml index d496d59df7..9c0549c11f 100644 --- a/data/release-notes/enterprise-server/3-9/0.yml +++ b/data/release-notes/enterprise-server/3-9/0.yml @@ -384,6 +384,8 @@ sections: After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9, I/O utilization will increase, and in some cases the instance's performance will be impacted. Reduced performance is due to the database server being upgraded from MySQL 5.7 to MySQL 8.0. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance)." - | {% data reusables.release-notes.upgrade-mysql8-cannot-start-up %} + - | + The Management Console may get stuck in a loop showing "Checking requirements..." when attempting to download an update. It is safe to proceed the update process manually via the command line. - | {% data reusables.release-notes.enterprise-backup-utils-encryption-keys %} - | From 6256513a145027524d76d439779943873063802f Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Tue, 8 Aug 2023 09:53:09 -0400 Subject: [PATCH 2/3] Adding known issue. --- data/release-notes/enterprise-server/3-9/1.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/data/release-notes/enterprise-server/3-9/1.yml b/data/release-notes/enterprise-server/3-9/1.yml index a313a5a014..5e61fa0530 100644 --- a/data/release-notes/enterprise-server/3-9/1.yml +++ b/data/release-notes/enterprise-server/3-9/1.yml @@ -102,6 +102,8 @@ sections: After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9, I/O utilization will increase, and in some cases the instance's performance will be impacted. Reduced performance is due to the database server being upgraded from MySQL 5.7 to MySQL 8.0. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance)." - | {% data reusables.release-notes.upgrade-mysql8-cannot-start-up %} + - | + The Management Console may get stuck in a loop showing "Checking requirements..." when attempting to download an update. It is safe to proceed the update process manually via the command line. - | When enabling CodeQL via default setup [at scale](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-at-scale), some checks related to GitHub Actions are omitted, potentially preventing the process from completing. - | From c7ba5e96fb5146b4950001f23726e5a26a6c2485 Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Tue, 8 Aug 2023 09:53:31 -0400 Subject: [PATCH 3/3] Adding known issue --- data/release-notes/enterprise-server/3-9/2.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/data/release-notes/enterprise-server/3-9/2.yml b/data/release-notes/enterprise-server/3-9/2.yml index d1a001fa59..52e1c856e5 100644 --- a/data/release-notes/enterprise-server/3-9/2.yml +++ b/data/release-notes/enterprise-server/3-9/2.yml @@ -11,6 +11,8 @@ sections: After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9, I/O utilization will increase, and in some cases the instance's performance will be impacted. Reduced performance is due to the database server being upgraded from MySQL 5.7 to MySQL 8.0. For more information, see "[AUTOTITLE](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/known-issues-with-upgrades-to-your-instance)." - | {% data reusables.release-notes.upgrade-mysql8-cannot-start-up %} + - | + The Management Console may get stuck in a loop showing "Checking requirements..." when attempting to download an update. It is safe to proceed the update process manually via the command line. - | When enabling CodeQL via default setup [at scale](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning-at-scale), some checks related to GitHub Actions are omitted, potentially preventing the process from completing. - |