Bug 1279281 - CoprKeygenRequestError: Failed to create key-pair for user: sergiomb, project:kde4for23
Summary: CoprKeygenRequestError: Failed to create key-pair for user: sergiomb, project...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Copr
Classification: Community
Component: backend
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Valentin Gologuzov
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-09 02:37 UTC by Sergio Basto
Modified: 2015-12-01 06:05 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-18 11:34:13 UTC
Embargoed:


Attachments (Terms of Use)

Description Sergio Basto 2015-11-09 02:37:59 UTC
[2015-11-09 02:26:46,814][  INFO][PID:28141] Success building kde-workspace
[2015-11-09 02:26:46,817][  INFO][PID:28141] Going to sign pkgs from source: BuildJob<id: 138231, owner: sergiomb, project: kde4for23, git branch: f23, git_hash: 0322ad90538b01a7848a2aa53cace32bb7e3cf12, status: 3 > in chroot: /var/lib/copr/public_html/results/sergiomb/kde4for23/fedora-23-x86_64
[2015-11-09 02:27:47,103][ ERROR][PID:28141] failed to sign packages built from `BuildJob<id: 138231, owner: sergiomb, project: kde4for23, git branch: f23, git_hash: 0322ad90538b01a7848a2aa53cace32bb7e3cf12, status: 3 >` with error


https://copr-be.cloud.fedoraproject.org/results/sergiomb/kde4for23/fedora-23-x86_64/00138231-kde-workspace/mockchain.log.gz

Comment 1 Miroslav Suchý 2015-11-09 10:21:33 UTC
*nod*
This happen when submitting first build in project. It somehow fail, but then create the key and next build goes without problem.
There is something obviously ordered incorrrectly.

Comment 2 Miroslav Suchý 2015-11-18 11:34:13 UTC
Fixed in commit f0f69ab.

Now we create gpg key right after you create project.
However the GPG key creation takes some time (e.g. minute) so if you send first build really soon you still hit this behaviour.


Note You need to log in before you can comment on or make changes to this bug.