Issue #652: Forking doesn't work - copr

copr / copr

#652 Forking doesn't work

Closed: Fixed 4 years ago by thrnciar. Opened 5 years ago by praiskup.

From https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org/thread/YDRGTRRUZGTSDJI27OCYVAUPYAJKVNCW/

This [1] is a forked project of python3.8 [2]; inside there are all
forked packages previously built but, if i require a new build for
testing Python 3.8, are not used the packages from the project [3] (i
see Python 3.7.3 as dependency).

What am I doing wrong?

[1] https://copr.fedorainfracloud.org/coprs/sagitter/python3.8/
[2] https://copr.fedorainfracloud.org/coprs/g/python/python3.8/
[3]
https://copr-be.cloud.fedoraproject.org/results/sagitter/python3.8/fedora-rawhide-x86_64/00881156-future/

Regards.

sagitter commented 5 years ago

Currently, it's added an external repository to bypass the issue:

External Repository List

The following repositories are accessible during builds

https://copr-be.cloud.fedoraproject.org/results/@python/python3.8_gdb_bootstrap/fedora-rawhide-$basearch/
https://copr-be.cloud.fedoraproject.org/results/@python/python3.8/fedora-rawhide-$basearch/

sagitter commented 5 years ago

From https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.org/thread/YDRGTRRUZGTSDJI27OCYVAUPYAJKVNCW/
This [1] is a forked project of python3.8 [2]; inside there are all
forked packages previously built but, if i require a new build for
testing Python 3.8, are not used the packages from the project [3] (i
see Python 3.7.3 as dependency).

What am I doing wrong?

[1] https://copr.fedorainfracloud.org/coprs/sagitter/python3.8/
[2] https://copr.fedorainfracloud.org/coprs/g/python/python3.8/
[3]
https://copr-be.cloud.fedoraproject.org/results/sagitter/python3.8/fedora-rawhide-x86_64/00881156-future/

Regards.

Link [3] as example of this issue: https://copr-be.cloud.fedoraproject.org/results/sagitter/python3.8/fedora-rawhide-x86_64/00881671-future/

frostyx commented 5 years ago

All the packages are 404, for example https://copr-be.cloud.fedoraproject.org/
results/sagitter/python3.8/
I guess the forking process didn't work correctly.

With an interesting exception for python-cornice, which seems to be the only package, that forked.

frostyx commented 5 years ago

There is an error from logs

[2019-04-09 18:48:18,050][  INFO][backend.actions][actions.py:run:466] Executing: <Action: {'action_type': 7, 'created_on': 1554835783, 'data': '{"user": "sagitter", "copr": "python3.8", "builds_map": {"srpm-builds": ["00880415", "00880770"], "fedora-rawhide-x86_64": ["00880415-python-cornice", "00880770-python-cornice"]}}', 'ended_on': None, 'id': 270275, 'message': None, 'new_value': 'sagitter/python3.8', 'object_id': None, 'object_type': 'copr', 'old_value': '@python/python3.8', 'result': 0}>
[2019-04-09 18:48:18,051][  INFO][backend.actions][actions.py:handle_fork:106] Action fork copr
[2019-04-09 18:53:18,166][ ERROR][backend.actions][actions.py:generate_gpg_key:327] can't convert <class 'backend.exceptions.CoprKeygenRequestError'>
Traceback (most recent call last):
  File "/usr/share/copr/backend/actions.py", line 324, in generate_gpg_key
    create_user_keys(ownername, projectname, self.opts)
  File "/usr/share/copr/backend/sign.py", line 166, in create_user_keys
    request=query, response=response)
backend.exceptions.CoprKeygenRequestError: Failed to create key-pair for user: sagitter, project:python3.8, 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>

request to copr-keygen: {'url': 'http://172.25.33.41/gen_key', 'data': '{"name_real": "sagitter_python3.8", "name_email": "sagitter#python3.8@copr.fedorahosted.org"}', 'method': 'post'}


[2019-04-09 18:53:18,200][ ERROR][backend.actions][actions.py:handle_fork:166] Failure during project forking
[2019-04-09 18:53:18,200][ ERROR][backend.actions][actions.py:handle_fork:167] There are no gpg keys for user sagitter in keyring
return code 1 after invocation of: ['sudo', '/bin/sign', '-u', 'sagitter#python3.8@copr.fedorahosted.org', '-p']
stderr:
stdout: unknown key: sagitter#python3.8@copr.fedorahosted.org


[2019-04-09 18:53:18,201][ ERROR][backend.actions][actions.py:handle_fork:168] Traceback (most recent call last):
  File "/usr/share/copr/backend/actions.py", line 126, in handle_fork
    get_pubkey(data["user"], data["copr"], pubkey_path)
  File "/usr/share/copr/backend/sign.py", line 54, in get_pubkey
    cmd=cmd, stdout=stdout, stderr=stderr)
backend.exceptions.CoprSignNoKeyError: There are no gpg keys for user sagitter in keyring
return code 1 after invocation of: ['sudo', '/bin/sign', '-u', 'sagitter#python3.8@copr.fedorahosted.org', '-p']
stderr:
stdout: unknown key: sagitter#python3.8@copr.fedorahosted.org



[2019-04-09 18:53:18,201][  INFO][backend.actions][actions.py:run:510] Action result: {'id': 270275, 'result': 2}

frostyx commented 5 years ago

Thank you for the report @sagitter,
from the logs it is obvious, that request for generating GPG key for your new project timeouted, therefore when copr-backend tried to sign the forked packages, it failed because there was no key (yet). I've checked, and the key is there, so I wanted to recommend you to fork the original python/python3.8 project into this already existing sagitter/python3.8, but I can see, that you already did that.

I've created PR#663 to avoid such issues in the future.