Skip to content
GitLab
Next
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,330
    • Merge requests 1,330
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #20069
Closed
Open
Issue created Nov 06, 2017 by Drew Blessing@dblessingDeveloper

Create Rake task to verify all encrypted data can be decrypted with instance's keys

We often see issues with errors such as OpenSSL::Cipher::CipherError (bad decrypt): in customer's HA environments. Our docs mention that /etc/gitlab/gitlab-secrets.json should be synced across all servers but it must be easy to miss. We should add a Rake task that will iterate through all encrypted data - project import data, CI variables, (and more?). If anything cannot be decrypted print out some info (type, id?). This should tell us reasonably well if any other instances in the cluster have differing keys.

Assignee
Assign to
Time tracking