Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #2356

Closed
Open
Created Dec 23, 2012 by Administrator@rootOwner

username collision when upgrading

Created by: repsejnworb

The "work out a username based on the email"-feature doesn't work very well if there are several users with the same initializing name in their email:

[email protected] [email protected]

This would cause: Usernames for users:rake aborted! Validation failed: Username has already been taken

After this error you will have to set the username of any user where it was already set to NULL and you also have to remove and namespace that was created for any user, else you run into: Usernames for users:rake aborted! Validation failed: Path has already been taken

Assignee
Assign to
Time tracking