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
  • #6387

Closed
Open
Created Feb 23, 2014 by Administrator@rootOwner

Orphaned deploy keys don't get deleted

Created by: m-o-e

Steps to reproduce:

  1. Create project, add one deploy key.
  2. Delete project

Expected behaviour: The orphaned deploy key is deleted from the database and authorized_keys.

Observed behaviour: The deploy key sticks around in the database and authorized_keys file and is effectively blocked from further use. I.e. it doesn't show up in the list of available deploy keys because it's not in a "project you have access to" anymore (the project was deleted). And it can not be re-added as a new deploy key because it still exists in the database.

Assignee
Assign to
Time tracking