#491 No gpg-agent running on copr-keygen-dev
Closed: Fixed 4 years ago by praiskup. Opened 5 years ago by frostyx.

When trying to sign something with copr-keygen-dev, it fails with

2019-01-10 13:10:29,937 INFO[logic:/usr/lib/python3.6/site-packages/copr_keygen/logic.py:140]: returncode: 2
2019-01-10 13:10:29,938 INFO[logic:/usr/lib/python3.6/site-packages/copr_keygen/logic.py:141]: stdout: b''
2019-01-10 13:10:29,938 INFO[logic:/usr/lib/python3.6/site-packages/copr_keygen/logic.py:142]: stderr: b"gpg: can't connect to the agent: IPC connect call failed\ngpg: agent_genkey failed: No agent running\ngpg: key generation failed: No agent running\n"

I found out, that on the production istance there is gpg-agent running, so I've tried to run it similarly

su copr-signer
gpg-agent --homedir /var/lib/copr-keygen/gnupg --use-standard-socket --daemon

but it doesn't seem to help.


This is likely going to be a selinux issue. Please, check SELinux type on files in /var/lib/copr-keygen.

selinux issue

On production, somebody done
cd /var/lib/copr-keygen/
chcon -R -t httpd_var_lib_t .

hmm, there was old copr-selinux. It was likely not build for F28 at all. rebuilding.

This is likely resolved; we run enforcing selinux on keygen.

Metadata Update from @praiskup:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata