diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-17 12:07:12 +0000 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-05-17 12:07:12 +0000 |
| commit | 43771438e9ccf20d1b6cf12b690e63844d7c3d49 (patch) | |
| tree | 147aefba22d99be62ff3c112f50e205e486e58c7 /doc/administration | |
| parent | eeb25534bae1021f5b7940138ee56dea8fc79949 (diff) | |
| download | gitlab-ce-43771438e9ccf20d1b6cf12b690e63844d7c3d49.tar.gz | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration')
| -rw-r--r-- | doc/administration/gitaly/troubleshooting.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/administration/gitaly/troubleshooting.md b/doc/administration/gitaly/troubleshooting.md index dbbd348556c..ef1f4e06595 100644 --- a/doc/administration/gitaly/troubleshooting.md +++ b/doc/administration/gitaly/troubleshooting.md @@ -400,6 +400,10 @@ To resolve this, remove the `noexec` option from the file system mount. An alter 1. Add `gitaly['runtime_dir'] = '<PATH_WITH_EXEC_PERM>'` to `/etc/gitlab/gitlab.rb` and specify a location without `noexec` set. 1. Run `sudo gitlab-ctl reconfigure`. +### Commit signing fails with `invalid argument: signing key is encrypted` or `invalid data: tag byte does not have MSB set.` + +Because Gitaly commit signing is headless and not associated with a specific user, the GPG signing key must be created without a passphrase, or the passphrase must be removed before export. + ## Troubleshoot Praefect (Gitaly Cluster) The following sections provide possible solutions to Gitaly Cluster errors. |