diff --git a/data/release-notes/enterprise-server/3-4/2.yml b/data/release-notes/enterprise-server/3-4/2.yml
index c012e6aada14..97fd1a49ef1e 100644
--- a/data/release-notes/enterprise-server/3-4/2.yml
+++ b/data/release-notes/enterprise-server/3-4/2.yml
@@ -29,6 +29,7 @@ sections:
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - |
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
 
   deprecations:
     - heading: Deprecation of GitHub Enterprise Server 3.0
diff --git a/data/release-notes/enterprise-server/3-4/3.yml b/data/release-notes/enterprise-server/3-4/3.yml
index d77546c1d37f..8903216825fb 100644
--- a/data/release-notes/enterprise-server/3-4/3.yml
+++ b/data/release-notes/enterprise-server/3-4/3.yml
@@ -36,3 +36,4 @@ sections:
     - Resource limits that are specific to processing pre-receive hooks may cause some pre-receive hooks to fail.
     - |
       After registering a self-hosted runner with the `--ephemeral` parameter on more than one level (for example, both enterprise and organization), the runner may get stuck in an idle state and require re-registration. [Updated: 2022-06-17]
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4 releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
diff --git a/data/release-notes/enterprise-server/3-4/4.yml b/data/release-notes/enterprise-server/3-4/4.yml
index ad0ea2883ec2..f8723731eeb3 100644
--- a/data/release-notes/enterprise-server/3-4/4.yml
+++ b/data/release-notes/enterprise-server/3-4/4.yml
@@ -33,3 +33,4 @@ sections:
       To work around this problem, you can take one of the two following actions.
       - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute.
       - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL.
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.
diff --git a/data/release-notes/enterprise-server/3-4/5.yml b/data/release-notes/enterprise-server/3-4/5.yml
index 96a1d9f3149c..f43a19ffde2d 100644
--- a/data/release-notes/enterprise-server/3-4/5.yml
+++ b/data/release-notes/enterprise-server/3-4/5.yml
@@ -32,3 +32,4 @@ sections:
       To work around this problem, you can take one of the two following actions.
       - Reconfigure the IdP by uploading a static copy of the SAML metadata without the `WantAssertionsEncrypted` attribute.
       - Copy the SAML metadata, remove `WantAssertionsEncrypted` attribute, host it on a web server, and reconfigure the IdP to point to that URL.
+    - After upgrading to {% data variables.product.prodname_ghe_server %} 3.4, releases may appear to be missing from repositories. This can occur when the required Elasticsearch index migrations have not successfully completed.