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

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Upgrade 5.4 -> 6.0 bug duplicate deploy keys not removed

Closed

Upgrade 5.4 -> 6.0 bug duplicate deploy keys not removed

Created by: samrocketman

This is a conversation from IRC. I'm filing it on others' behalf so that it is documented to be looked into.

06:13 < morsik> hi...
06:13 < morsik> i migrated gitlab 5.4 to 6.0 and deploy keys doesn't works...
06:13 < morsik> now i'm at 6.1 and nothing changed
06:14 < morsik> using https://git.localdomain/api/v3/internal/discover?key_id=2   returns:   {"message":"404 Not found"}
06:14 < morsik> (id 2 is in authorized_keys under deployment key)
06:15 < morsik> oh well...
06:15 < morsik> i removed duplicated in authorized_keys and it looks like it works now
06:15 < morsik> :D
06:15 -!- mneorr [~mneorr@212.91.105.105] has quit [Ping timeout: 245 seconds]
06:16 < honestly> morsik: yes, duplicate keys are the problem
06:16 < honestly> morsik: did you miss running the rake task to remove duplicate keys?
06:16 < morsik> honestly: nope, i didn't missed it
06:16 < morsik> i remember, it even asked if i'm sure to remove duplicates
06:18 < honestly> hmm, then I guess the rake task doesn't touch deploy keys
06:19 < honestly> consider filing an issue

If a fix is created for this it should be applied to 6.0.

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: jvanbaarsen

      @Razer6 What do you think? is this still an issue?

      By Administrator on 2014-01-09T11:12:24 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: jvanbaarsen

      @Razer6 I ant reproduce this issue, what do you think?

      By Administrator on 2014-02-28T07:33:14 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Razer6

      Let's close it. If someone comes up with the same issue lets open a new one.

      By Administrator on 2014-02-28T07:41:50 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: