From 72a7eddd9bf5630737e9ab2420905b661ac44f22 Mon Sep 17 00:00:00 2001
From: bonsohi <31749534+bonsohi@users.noreply.github.com>
Date: Fri, 10 Dec 2021 15:29:15 -0800
Subject: [PATCH] actions workaround alert for 3.3.0 (#23591)

* actions workaround alert

* Update known issue

Co-authored-by: Ethan P <56270045+ethanpalm@users.noreply.github.com>
---
 data/release-notes/enterprise-server/3-3/0.yml | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/data/release-notes/enterprise-server/3-3/0.yml b/data/release-notes/enterprise-server/3-3/0.yml
index 7641f7af58..9dec376333 100644
--- a/data/release-notes/enterprise-server/3-3/0.yml
+++ b/data/release-notes/enterprise-server/3-3/0.yml
@@ -1,5 +1,5 @@
 date: '2021-12-07'
-intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."
+intro: For upgrade instructions, see "[Upgrading {% data variables.product.prodname_ghe_server %}](/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrading-github-enterprise-server)."<br><br>**Note:** We are aware of an issue where {% data variables.product.prodname_actions %} may fail to start automatically following the upgrade to {% data variables.product.prodname_ghe_server %} 3.3. To resolve, connect to the appliance via SSH and run the `ghe-actions-start` command.
 sections:
   features:
     - heading: Security Manager role
@@ -240,6 +240,7 @@ sections:
   #   - PLACEHOLDER
 
   known_issues:
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.3, {% data variables.product.prodname_actions %} may fail to start automatically. To resolve this issue, connect to the appliance via SSH and run the `ghe-actions-start` command.
     - On a freshly set up {% data variables.product.prodname_ghe_server %} instance without any users, an attacker could create the first admin user.
     - Custom firewall rules are removed during the upgrade process.
     - Git LFS tracked files [uploaded through the web interface](https://github.com/blog/2105-upload-files-to-your-repositories) are incorrectly added directly to the repository.