Merge branch 'mcelicalderonG-wit-update-upgrade-docs' into 'master'

Update docs for 17.8 upgrades

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/183890



Merged-by: Marcin Sedlak-Jakubowski <msedlakjakubowski@gitlab.com>
Reviewed-by: Marcin Sedlak-Jakubowski <msedlakjakubowski@gitlab.com>
Co-authored-by: Mario Celi <mcelicalderon@gitlab.com>

doc/update/versions/gitlab_17_changes.md

@@ -218,6 +218,33 @@ For more information, see [issue 480328](https://gitlab.com/gitlab-org/gitlab/-/
    gitlab-rake db:migrate:up:ci VERSION=20241028085044
    ```
 
+## Issues to be aware of when upgrading to 17.8
+
+- Migration failures when upgrading to GitLab 17.8.
+
+  When upgrading to 17.8, there is a slight chance of encountering an error. During the migration process, you might see an error message like the one below:
+
+  ```shell
+  ERROR:  duplicate key value violates unique constraint "work_item_types_pkey"
+  DETAIL:  Key (id)=(1) already exists.
+  ```
+
+  The migration producing the error would be `db/post_migrate/20241218223002_fix_work_item_types_id_column_values.rb`.
+
+  This error occurs because in some cases, records in the `work_item_types` table were not created in the database
+  in the same order as they were added to the application.
+
+  To safely resolve this issue, follow these steps:
+
+  1. **Only do this if you got this error when trying to upgrade to 17.8.**
+     Run the following SQL query in your `gitlab_main` database:
+
+      ```sql
+      UPDATE work_item_types set id = (id * 10);
+      ```
+
+  1. Retry running the failed migration. It should now succeed.
+
 ## 17.8.0
 
 - In GitLab 17.8.0, GitLab agent server for Kubernetes (KAS) does not start with the default settings on the GitLab Linux package (Omnibus) and Docker installations.