jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Remove a resolved known issue from 3.13.4 release notes (#52474)

Browse Source 
Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
This commit is contained in:
Pallavi
2024-10-23 04:44:03 -07:00
committed by GitHub
parent ea1b1f490b
commit 80e1e9852c
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
data/release-notes/enterprise-server/3-13/4.yml
View File

@@ -72,7 +72,7 @@ sections:
When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed. When restoring from a backup snapshot, a large number of `mapper_parsing_exception` errors may be displayed.
- | - |
Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run. Services may respond with a `503` status due to an out of date `haproxy` configuration. This can usually be resolved with a `ghe-config-apply` run.
- |
Instance setup in AWS with IMDSv2 enforced fails if no public IP is present.
- | - |
For customers using Secret Scanning, internal jobs were created and not worked that could contribute to performance issues. For customers using Secret Scanning, internal jobs were created and not worked that could contribute to performance issues.
errata:
- 'The "[Known issues](/admin/release-notes#3.13.4-known-issues)" section previously indicated that `Instance setup in AWS with IMDSv2 enforced fails if no public IP is present` is still an issue. The issue is resolved and is documented in the "[Bug fixes](/admin/release-notes#3.13.4-bugs)" section. [Updated: 2024-09-30]'