From 4c1b259721a36d4e4792c612fef507c6068bbd1c Mon Sep 17 00:00:00 2001 From: "Roger D. Winans" Date: Mon, 26 Sep 2022 04:05:30 -0400 Subject: [PATCH] Add known issue: GHES hotpatch 3.6.2 may fail (#31079) Co-authored-by: Matt Pollard --- data/release-notes/enterprise-server/3-6/1.yml | 6 ++++++ data/release-notes/enterprise-server/3-6/2.yml | 6 ++++++ 2 files changed, 12 insertions(+) diff --git a/data/release-notes/enterprise-server/3-6/1.yml b/data/release-notes/enterprise-server/3-6/1.yml index f31b9cb734b2..ee77163e7154 100644 --- a/data/release-notes/enterprise-server/3-6/1.yml +++ b/data/release-notes/enterprise-server/3-6/1.yml @@ -31,3 +31,9 @@ sections: - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality. - In some cases, users cannot convert existing issues to discussions. - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter. + - | + Hotpatch upgrades to {% data variables.product.prodname_ghe_server %} 3.6.2 may fail. Upgrades with the full `.pkg` are unaffected. If the upgrade fails for your instance, you can work around the issue in one of two ways. + 1. SSH into the affected node and run `sudo dpkg --configure -a`, then start the upgrade again. + 2. Alternatively, run the full `.pkg` upgrade. + + If you're unable to upgrade, or if you need further assistance, contact GitHub Support. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-09-26] \ No newline at end of file diff --git a/data/release-notes/enterprise-server/3-6/2.yml b/data/release-notes/enterprise-server/3-6/2.yml index 73600e1445f8..19a2c1a2cde7 100644 --- a/data/release-notes/enterprise-server/3-6/2.yml +++ b/data/release-notes/enterprise-server/3-6/2.yml @@ -40,3 +40,9 @@ sections: - In a repository's settings, enabling the option to allow users with read access to create discussions does not enable this functionality. - In some cases, users cannot convert existing issues to discussions. - Custom patterns for secret scanning have `.*` as an end delimiter, specifically in the "After secret" field. This delimiter causes inconsistencies in scans for secrets across repositories, and you may notice gaps in a repository's history where no scans completed. Incremental scans may also be impacted. To prevent issues with scans, modify the end of the pattern to remove the `.*` delimiter. + - | + Hotpatch upgrades to {% data variables.product.prodname_ghe_server %} 3.6.2 may fail. Upgrades with the full `.pkg` are unaffected. If the upgrade fails for your instance, you can work around the issue in one of two ways. + 1. SSH into the affected node and run `sudo dpkg --configure -a`, then start the upgrade again. + 2. Alternatively, run the full `.pkg` upgrade. + + If you're unable to upgrade, or if you need further assistance, contact GitHub Support. For more information, see "[Creating a support ticket](/support/contacting-github-support/creating-a-support-ticket)." [Updated: 2022-09-26] \ No newline at end of file