From 752fd5dd06e20f170d76bf57f972e9a8e2d70de1 Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Mon, 7 Aug 2023 17:37:26 -0400 Subject: [PATCH 1/5] Adding new known issue about upgrades being blocked Adding https://github.com/github/ghes/issues/7048 to known issues. --- data/release-notes/enterprise-server/3-10/0-rc1.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/data/release-notes/enterprise-server/3-10/0-rc1.yml b/data/release-notes/enterprise-server/3-10/0-rc1.yml index 5c71a1d82b..67f61df2d4 100644 --- a/data/release-notes/enterprise-server/3-10/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-10/0-rc1.yml @@ -225,8 +225,12 @@ sections: known_issues: # INCLUDE NOTES FOR RELEASE FROM "GHES Release Note Tracking" PROJECT'S "Known Issues" TAB + # https://github.com/github/ghes/issues/6877 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | We are aware of a known issue with `ghe-repl-promote` getting stuck on `Configuration phase 3`. This will be fixed when version 3.10.0 goes GA. + # https://github.com/github/ghes/issues/7048 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it + - | + We are aware of a known issue that prevents instances running GitHub Enterprise Server 3.9.0 or 3.9.1 from upgrading to the 3.10.0 release candidate. The workaround to this issue is to first upgrade to the 3.9.2 patch before upgrading to the 3.10.0 release candidate. This will be fixed when version 3.10.0 goes GA, so that instances running 3.9.0 or 3.9.1 can upgrade to 3.10.0. - | After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9 or 3.10, 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)." - | From 2a5f69a2426b69a6a26ac9645edddeeba981e579 Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Mon, 7 Aug 2023 17:45:08 -0400 Subject: [PATCH 2/5] Added known issues for search bug and pre-upgrade check --- data/release-notes/enterprise-server/3-10/0-rc1.yml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/data/release-notes/enterprise-server/3-10/0-rc1.yml b/data/release-notes/enterprise-server/3-10/0-rc1.yml index 67f61df2d4..a7be7c667a 100644 --- a/data/release-notes/enterprise-server/3-10/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-10/0-rc1.yml @@ -227,10 +227,13 @@ sections: # INCLUDE NOTES FOR RELEASE FROM "GHES Release Note Tracking" PROJECT'S "Known Issues" TAB # https://github.com/github/ghes/issues/6877 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | - We are aware of a known issue with `ghe-repl-promote` getting stuck on `Configuration phase 3`. This will be fixed when version 3.10.0 goes GA. + Promoting a replica with `ghe-repl-promote` gets stuck on `Configuration phase 3`. This will be fixed when version 3.10.0 becomes generally available. # https://github.com/github/ghes/issues/7048 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | - We are aware of a known issue that prevents instances running GitHub Enterprise Server 3.9.0 or 3.9.1 from upgrading to the 3.10.0 release candidate. The workaround to this issue is to first upgrade to the 3.9.2 patch before upgrading to the 3.10.0 release candidate. This will be fixed when version 3.10.0 goes GA, so that instances running 3.9.0 or 3.9.1 can upgrade to 3.10.0. + Instances running GitHub Enterprise Server 3.9.0 or 3.9.1 cannot upgrade to the 3.10.0 release candidate. The workaround to this issue is to first upgrade to the 3.9.2 patch before upgrading to the 3.10.0 release candidate. This will be fixed when version 3.10.0 goes GA, so that instances running 3.9.0 or 3.9.1 can upgrade to 3.10.0. + # https://github.com/github/mEAO/issues/1276 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it + - | + On an instance with GitHub Connect and Unified Search enabled, users will receive a 500 error after performing a GitHub.com search then selecting Advanced Search. This will be fixed when GitHub Enterprise Server 3.10.0 is generally available. - | After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9 or 3.10, 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)." - | From 60165b7852de1beff7732bfe26bc505105131559 Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Mon, 7 Aug 2023 19:31:58 -0400 Subject: [PATCH 3/5] Update data/release-notes/enterprise-server/3-10/0-rc1.yml Co-authored-by: Vanessa --- data/release-notes/enterprise-server/3-10/0-rc1.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/release-notes/enterprise-server/3-10/0-rc1.yml b/data/release-notes/enterprise-server/3-10/0-rc1.yml index a7be7c667a..2cef43900c 100644 --- a/data/release-notes/enterprise-server/3-10/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-10/0-rc1.yml @@ -233,7 +233,7 @@ sections: Instances running GitHub Enterprise Server 3.9.0 or 3.9.1 cannot upgrade to the 3.10.0 release candidate. The workaround to this issue is to first upgrade to the 3.9.2 patch before upgrading to the 3.10.0 release candidate. This will be fixed when version 3.10.0 goes GA, so that instances running 3.9.0 or 3.9.1 can upgrade to 3.10.0. # https://github.com/github/mEAO/issues/1276 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | - On an instance with GitHub Connect and Unified Search enabled, users will receive a 500 error after performing a GitHub.com search then selecting Advanced Search. This will be fixed when GitHub Enterprise Server 3.10.0 is generally available. + On an instance with GitHub Connect and unified search enabled, users will receive a `500` error after performing a GitHub.com search then selecting Advanced search. This will be fixed when GitHub Enterprise Server 3.10.0 is generally available. - | After an administrator upgrades from {% data variables.product.prodname_ghe_server %} 3.7 or 3.8 to 3.9 or 3.10, 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)." - | From b22ad73c3e3d3d47783560e8b6c6323b0a1c23af Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Mon, 7 Aug 2023 19:32:50 -0400 Subject: [PATCH 4/5] Update data/release-notes/enterprise-server/3-10/0-rc1.yml Co-authored-by: Vanessa --- data/release-notes/enterprise-server/3-10/0-rc1.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/release-notes/enterprise-server/3-10/0-rc1.yml b/data/release-notes/enterprise-server/3-10/0-rc1.yml index 2cef43900c..033710d3e2 100644 --- a/data/release-notes/enterprise-server/3-10/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-10/0-rc1.yml @@ -227,7 +227,7 @@ sections: # INCLUDE NOTES FOR RELEASE FROM "GHES Release Note Tracking" PROJECT'S "Known Issues" TAB # https://github.com/github/ghes/issues/6877 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | - Promoting a replica with `ghe-repl-promote` gets stuck on `Configuration phase 3`. This will be fixed when version 3.10.0 becomes generally available. + When promoting a replica with `ghe-repl-promote`, applying the configuration fails at `Configuration phase 3`. This will be fixed when version 3.10.0 becomes generally available. # https://github.com/github/ghes/issues/7048 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | Instances running GitHub Enterprise Server 3.9.0 or 3.9.1 cannot upgrade to the 3.10.0 release candidate. The workaround to this issue is to first upgrade to the 3.9.2 patch before upgrading to the 3.10.0 release candidate. This will be fixed when version 3.10.0 goes GA, so that instances running 3.9.0 or 3.9.1 can upgrade to 3.10.0. From 1fd220cb6989f9e13f226a7f5e6dcd6a47b314f4 Mon Sep 17 00:00:00 2001 From: David Jarzebowski Date: Mon, 7 Aug 2023 19:33:02 -0400 Subject: [PATCH 5/5] Update data/release-notes/enterprise-server/3-10/0-rc1.yml Co-authored-by: Vanessa --- data/release-notes/enterprise-server/3-10/0-rc1.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/data/release-notes/enterprise-server/3-10/0-rc1.yml b/data/release-notes/enterprise-server/3-10/0-rc1.yml index 033710d3e2..967f1bcc1c 100644 --- a/data/release-notes/enterprise-server/3-10/0-rc1.yml +++ b/data/release-notes/enterprise-server/3-10/0-rc1.yml @@ -230,7 +230,7 @@ sections: When promoting a replica with `ghe-repl-promote`, applying the configuration fails at `Configuration phase 3`. This will be fixed when version 3.10.0 becomes generally available. # https://github.com/github/ghes/issues/7048 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | - Instances running GitHub Enterprise Server 3.9.0 or 3.9.1 cannot upgrade to the 3.10.0 release candidate. The workaround to this issue is to first upgrade to the 3.9.2 patch before upgrading to the 3.10.0 release candidate. This will be fixed when version 3.10.0 goes GA, so that instances running 3.9.0 or 3.9.1 can upgrade to 3.10.0. + Instances running GitHub Enterprise Server 3.9.0 or 3.9.1 cannot upgrade to the 3.10.0 release candidate. The workaround to this issue is to first upgrade to the 3.9.2 patch before upgrading to the 3.10.0 release candidate. This will be fixed when version 3.10.0 becomes generally available, so that instances running 3.9.0 or 3.9.1 can upgrade to 3.10.0. # https://github.com/github/mEAO/issues/1276 - this will be resolved before GA; @davidjarzebowski will create a separate PR to remove it - | On an instance with GitHub Connect and unified search enabled, users will receive a `500` error after performing a GitHub.com search then selecting Advanced search. This will be fixed when GitHub Enterprise Server 3.10.0 is generally available.