diff options
Diffstat (limited to 'doc/user/profile/account/delete_account.md')
-rw-r--r-- | doc/user/profile/account/delete_account.md | 42 |
1 files changed, 25 insertions, 17 deletions
diff --git a/doc/user/profile/account/delete_account.md b/doc/user/profile/account/delete_account.md index 365f96b48b3..c116b1fc00d 100644 --- a/doc/user/profile/account/delete_account.md +++ b/doc/user/profile/account/delete_account.md @@ -1,7 +1,7 @@ --- type: howto stage: Manage -group: Authentication & Authorization +group: Authentication and Authorization info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments --- @@ -55,16 +55,17 @@ There are two options for deleting users: - **Delete user and contributions** When using the **Delete user** option, not all associated records are deleted with the user. -Here's a list of things that are **not** deleted: +Here's a list of things created by the user that are **not** deleted: -- Issues that the user created. -- Merge requests that the user created. -- Notes that the user created. -- Abuse reports that the user reported. -- Award emoji that the user created. +- Abuse reports +- Award emoji +- Epics +- Issues +- Merge requests +- Notes Instead of being deleted, these records are moved to a system-wide -user with the username "Ghost User", whose sole purpose is to act as a container +user with the username Ghost User, whose sole purpose is to act as a container for such records. Any commits made by a deleted user still display the username of the original user. @@ -81,14 +82,21 @@ is a sole owner of. Administrators can also request this behavior when deleting users from the [API](../../../api/users.md#user-deletion) or the Admin Area. -<!-- ## Troubleshooting +## Troubleshooting -Include any troubleshooting steps that you can foresee. If you know beforehand what issues -one might have when setting this up, or when something is changed, or on upgrading, it's -important to describe those, too. Think of things that may go wrong and include them here. -This is important to minimize requests for support, and to avoid doc comments with -questions that you know someone might ask. +### Deleting a user results in a PostgreSQL null value error -Each scenario can be a third-level heading, e.g. `### Getting error message X`. -If you have none to add when creating a doc, leave this section in place -but commented out to help encourage others to add to it in the future. --> +There is [a known issue](https://gitlab.com/gitlab-org/gitlab/-/issues/349411) that results +in users not being deleted, and the following error generated: + +```plaintext +ERROR: null value in column "user_id" violates not-null constraint +``` + +The error can be found in the [PostgreSQL log](../../../administration/logs.md#postgresql-logs) and +in the **Retries** section of the [background jobs view](../../admin_area/index.md#background-jobs) in the Admin Area. + +If the user being deleted used the [iterations](../../group/iterations/index.md) feature, such +as adding an issue to an iteration, you must use +[the workaround documented in the issue](https://gitlab.com/gitlab-org/gitlab/-/issues/349411#workaround) +to delete the user. |