From bdf6755e105335d378e37965e5d527286f59fcab Mon Sep 17 00:00:00 2001 From: Alvin Gounder Date: Mon, 21 Jul 2025 07:21:03 +0000 Subject: [PATCH 1/3] Add upgrade note about bug #550954 --- doc/update/versions/gitlab_18_changes.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/doc/update/versions/gitlab_18_changes.md b/doc/update/versions/gitlab_18_changes.md index 5ce64199e1edcf..38ce61c4128a9f 100644 --- a/doc/update/versions/gitlab_18_changes.md +++ b/doc/update/versions/gitlab_18_changes.md @@ -29,7 +29,12 @@ For additional information for Helm chart installations, see ### Geo installations 18.1.0 -- GitLab version 18.1.0 has a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.1.1 or later. +- GitLab version 18.1.0 has a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.1.2 or later. +- GitLab versions 18.1.0 and 18.1.1 will show errors in the postgresql logs like: `ERROR: relation "ci_job_artifacts" does not exist at ...`. + These errors in the logs will not affect the functioning of the instance but could trigger alarms on Geo Nodes. + To fix this, please upgrade to 18.1.2 or newer. + See [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954) + ## 18.0.0 @@ -58,6 +63,11 @@ For additional information for Helm chart installations, see - GitLab versions 18.0 through 18.0.2 have a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.0.3 or later. +- GitLab versions 18.0 through 18.0.2 will show errors in the postgresql logs like: `ERROR: relation "ci_job_artifacts" does not exist at ...`. + These errors in the logs will not affect the functioning of the instance but could trigger alarms on Geo Nodes. + To fix this, please upgrade to 18.1.2 or newer. + See [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954) + ### PRNG is not seeded error on Docker installations If you run GitLab on a Docker installation with a FIPS-enabled host, you -- GitLab From 3a19431df7a1e2e809f19a9f11a42692e9e11914 Mon Sep 17 00:00:00 2001 From: Alvin Gounder Date: Thu, 31 Jul 2025 06:33:23 +0000 Subject: [PATCH 2/3] Apply Evan's excellent suggestions --- doc/update/versions/gitlab_18_changes.md | 15 +++++++-------- 1 file changed, 7 insertions(+), 8 deletions(-) diff --git a/doc/update/versions/gitlab_18_changes.md b/doc/update/versions/gitlab_18_changes.md index 38ce61c4128a9f..c0cfca67d86d9d 100644 --- a/doc/update/versions/gitlab_18_changes.md +++ b/doc/update/versions/gitlab_18_changes.md @@ -30,11 +30,10 @@ For additional information for Helm chart installations, see ### Geo installations 18.1.0 - GitLab version 18.1.0 has a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.1.2 or later. -- GitLab versions 18.1.0 and 18.1.1 will show errors in the postgresql logs like: `ERROR: relation "ci_job_artifacts" does not exist at ...`. - These errors in the logs will not affect the functioning of the instance but could trigger alarms on Geo Nodes. - To fix this, please upgrade to 18.1.2 or newer. - See [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954) +- GitLab versions 18.1.0 and 18.1.1 show errors in the PostgreSQL logs such as `ERROR: relation "ci_job_artifacts" does not exist at ...`. + These errors in the logs can be safely ignored, but could trigger alarms on Geo Nodes. To resolve these errors, update to GitLab 18.1.2 or later. + For more information, see [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954). ## 18.0.0 @@ -63,10 +62,10 @@ For additional information for Helm chart installations, see - GitLab versions 18.0 through 18.0.2 have a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.0.3 or later. -- GitLab versions 18.0 through 18.0.2 will show errors in the postgresql logs like: `ERROR: relation "ci_job_artifacts" does not exist at ...`. - These errors in the logs will not affect the functioning of the instance but could trigger alarms on Geo Nodes. - To fix this, please upgrade to 18.1.2 or newer. - See [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954) +- GitLab versions 18.0 through 18.0.2 show errors in the PostgreSQL logs such as `ERROR: relation "ci_job_artifacts" does not exist at ...`. + + These errors in the logs can be safely ignored, but could trigger alarms on Geo Nodes. To resolve these errors, update to GitLab 18.1.2 or later. + For more information, see [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954). ### PRNG is not seeded error on Docker installations -- GitLab From 2afd060e928cfc1aa5c541a14f2e1da99932c361 Mon Sep 17 00:00:00 2001 From: Achilleas Pipinellis Date: Sat, 2 Aug 2025 22:23:50 +0200 Subject: [PATCH 3/3] Apply 2 suggestion(s) to 1 file(s) --- doc/update/versions/gitlab_18_changes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/update/versions/gitlab_18_changes.md b/doc/update/versions/gitlab_18_changes.md index c0cfca67d86d9d..3a8a7c1ff959f7 100644 --- a/doc/update/versions/gitlab_18_changes.md +++ b/doc/update/versions/gitlab_18_changes.md @@ -30,7 +30,7 @@ For additional information for Helm chart installations, see ### Geo installations 18.1.0 - GitLab version 18.1.0 has a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.1.2 or later. -- GitLab versions 18.1.0 and 18.1.1 show errors in the PostgreSQL logs such as `ERROR: relation "ci_job_artifacts" does not exist at ...`. +- GitLab versions 18.1.0 and 18.1.1 show errors in the PostgreSQL logs such as `ERROR: relation "ci_job_artifacts" does not exist at ...`. These errors in the logs can be safely ignored, but could trigger alarms on Geo Nodes. To resolve these errors, update to GitLab 18.1.2 or later. For more information, see [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954). @@ -62,7 +62,7 @@ For additional information for Helm chart installations, see - GitLab versions 18.0 through 18.0.2 have a known issue where Git operations that are proxied from a secondary Geo site fail with HTTP 500 errors. To resolve, upgrade to GitLab 18.0.3 or later. -- GitLab versions 18.0 through 18.0.2 show errors in the PostgreSQL logs such as `ERROR: relation "ci_job_artifacts" does not exist at ...`. +- GitLab versions 18.0 through 18.0.2 show errors in the PostgreSQL logs such as `ERROR: relation "ci_job_artifacts" does not exist at ...`. These errors in the logs can be safely ignored, but could trigger alarms on Geo Nodes. To resolve these errors, update to GitLab 18.1.2 or later. For more information, see [issue #550954](https://gitlab.com/gitlab-org/gitlab/-/issues/550954). -- GitLab