Hi, I've been trying to get a custom kernel built for some testing. Two things; both related to signing... (maybe to each other?) My first build [1] made the packages correctly, but failed with [2] --- Traceback (most recent call last): File "/usr/share/copr/backend/mockremote/__init__.py", line 214, in sign_built_packages log=self.log File "/usr/share/copr/backend/sign.py", line 121, in sign_rpms_in_dir create_user_keys(username, projectname, opts) File "/usr/share/copr/backend/sign.py", line 167, in create_user_keys request=query, response=response) CoprKeygenRequestError: Failed to create key-pair for user: iwienand, project:kernel-4.6.4-301.rhbz1361414, status_code: 504, response: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>504 Gateway Timeout</title> </head><body> <h1>Gateway Timeout</h1> <p>The gateway did not receive a timely response from the upstream server or application.</p> </body></html> --- The second build worked correctly [3] but when trying to install from the repo, dnf reports that the package is not signed --- ... The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: Package kernel-4.6.4-301.rhbz1361414.fc24.x86_64.rpm is not signed --- This seems repeatable -- this happened to me previously, so I deleted my project and tried the whole thing again and same result (first build failed, second build reporting as unsigned). [1] https://copr.fedorainfracloud.org/coprs/iwienand/kernel-4.6.4-301.rhbz1361414/build/438285/ [2] https://copr-be.cloud.fedoraproject.org/results/iwienand/kernel-4.6.4-301.rhbz1361414/fedora-24-x86_64/00438285-kernel/mockchain.log.gz [3] https://copr.fedorainfracloud.org/coprs/iwienand/kernel-4.6.4-301.rhbz1361414/build/438368/
I have also observed the same behavior.
The second build should be alright (all packages signed). You should be able to install the kernel package from your project after deleting the first build and running 'dnf clean packages' on your machine. The first operation will remove records of the unsigned packages from your project's repodata. The second operation will clean your local package cache. The reason for the first build failure was that the new key for the project was not generated soon enough to be available for the signing procedure. The key generation started after the build was "finished" and not immediately after the project creation, which is the usual procedure. That happened because our action queue was blocked most of the last week due to a bug in forking code. There happened to be an infinite signing loop upon a few packages. We are working on a solution. Sorry for the problems.
*** Bug 1365104 has been marked as a duplicate of this bug. ***
The described problem with queue jamming was fixed by: https://github.com/fedora-copr/copr/commit/18650210
copr-backend-1.92-1.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-76bd2fb756
copr-backend-1.92-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8c6f580ff7
copr-backend-1.92-1.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-76bd2fb756
copr-backend-1.92-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8c6f580ff7
New Copr has been released.