Learn more about these different git repos.
Other Git URLs
[2022-03-22 03:46:39,925][ ERROR]: failed to sign rpm: /var/lib/copr/public_html/results/@rubygems/rubygems/epel-9-x86_64/03494467-rubygem-realm-sns/rubygem-realm-sns-0.7.4-1.el9.noarch.rpm Traceback (most recent call last): File "/usr/lib/python3.10/site-packages/copr_backend/sign.py", line 169, in sign_rpms_in_dir _sign_one(rpm, create_gpg_email(username, projectname), File "/usr/lib/python3.10/site-packages/copr_backend/sign.py", line 90, in _sign_one raise CoprSignError( copr_backend.exceptions.CoprSignError: Failed to sign /var/lib/copr/public_html/results/@rubygems/rubygems/epel-9-x86_64/03494467-rubygem-realm-sns/rubygem-realm-sns-0.7.4-1.el9.noarch.rpm by user @rubygems#rubygems@copr.fedorahosted.org return code 2 after invocation of: ['/bin/sign', '-h', 'sha256', '-u', '@rubygems#rubygems@copr.fedorahosted.org', '-r', '/var/lib/copr/public_html/results/@rubygems/rubygems/epel-9-x86_64/03494467-rubygem-realm-sns/rubygem-realm-sns-0.7.4-1.el9.noarch.rpm'] stderr: stdout: gpg: WARNING: server 'gpg-agent' is older than us (2.3.3 < 2.3.4)
This happened while mass re-signing epel-9 in @rubygems/rubygems.
And probably a follow-up error:
[2022-03-22 03:46:41,785][ ERROR]: Rpm sign failed, affected rpms: ['/var/lib/copr/public_html/results/@rubygems/rubygems/epel-9-x86_64/03494467-rubygem-realm-sns/rubygem-realm-sns-0.7.4-1.el9.noarch.rpm'] Traceback (most recent call last): File "/usr/bin/copr_fix_gpg.py", line 115, in fix_copr sign_rpms_in_dir(owner, coprname, builddir_path, chroot, opts, log) File "/usr/lib/python3.10/site-packages/copr_backend/sign.py", line 178, in sign_rpms_in_dir raise CoprSignError("Rpm sign failed, affected rpms: {}" copr_backend.exceptions.CoprSignError: Rpm sign failed, affected rpms: ['/var/lib/copr/public_html/results/@rubygems/rubygems/epel-9-x86_64/03494467-rubygem-realm-sns/rubygem-realm-sns-0.7.4-1.el9.noarch.rpm']
This is on BE? Hmm, the package was updated on 2022-02-16
2022-02-16T19:35:26+0000 DEBUG ---> Package gnupg2.x86_64 2.3.3-1.fc35 will be upgraded 2022-02-16T19:35:26+0000 DEBUG ---> Package gnupg2.x86_64 2.3.4-1.fc35 will be an upgrade
This is on BE?
Yes, /var/log/copr-backend/fix_gpg.log
Hmm, the package was updated on 2022-02-16 2022-02-16T19:35:26+0000 DEBUG ---> Package gnupg2.x86_64 2.3.3-1.fc35 will be upgraded 2022-02-16T19:35:26+0000 DEBUG ---> Package gnupg2.x86_64 2.3.4-1.fc35 will be an upgrade
Perhaps dnf automatic? But this error happened yesterday? I don't get the correlation, can you elaborate?
Metadata Update from @praiskup: - Issue assigned to frostyx
IIRC we decided to deal with this issue by attempting to sign the package multiple times if the original request fails. Modified in PR#2177
Commit bb08872 fixes this issue
Login to comment on this ticket.