Hello,
for (at least) a few days, each time I use Koji, either from the command line, or directly on SSL Web site (https://koji.fedoraproject.org/koji/login), it times out and nothing happens. For instance: [build@vm13 devel]$ fedora-cvs R-msm [build@vm13 devel]$ cd R-msm/devel [build@vm13 devel]$ make tag [build@vm13 devel]$ make build /usr/bin/koji build dist-rawhide 'cvs:// cvs.fedoraproject.org/cvs/pkgs?rpms/R-msm/devel#R-msm-0_9_5-2_fc14' timeout: (110, 'Operation timed out.') make: *** [build] Error 1
My FAS certificates had expired, and I had to renew it (directly from https://admin.fedoraproject.org/accounts/home). I downloaded the new server-side certificate and stored it as ~/.fedora.cert Then, I downloaded a new client certificate for the browser: [build@vm13 devel]$ fedora-packager-setup and checked the new server-side certificate: [build@vm13 ~]$ fedora-cert -v .fedora.cert Verifying Certificate cert expires: 2011-01-10 CRL Checking not implemented yet
I see the same symptoms as in https://bugzilla.redhat.com/show_bug.cgi?id=542767#c13 and as in http://www.spinics.net/lists/fedora-packaging/msg06987.html(though, it is not transient in my case: that issue is persistent for me)
=============== Moreover: * I have a SSH-RSA key (in ~/.ssh/id_rsa, there does not seem to have an expiration date), for which I've added the public key to my FAS account ( http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/...). Could that SSH-RSA key interfere with the ~/.fedora.cert certificate? * I have a GPG key, still valid, for which I have added the public key to my FAS account ( http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/... ).
====
Any help would be welcome!
Thanks in advance
Best Regards
Denis
I eventually found a work around, allowing to circumvent the time-out (error code 110) of Koji. The work around consists in forcing the "authtype=noauth" option: cat /etc/koji.conf [...] ;configuration for SSL authentication authtype = noauth [...]
Now, when trying to build from Fedora checked-out directory, I get the following error: $ /usr/bin/koji build dist-6E-epel 'cvs:// cvs.fedoraproject.org/cvs/pkgs?rpms/R-msm/EL-6#R-msm-0_9_1-2_el6' GenericError: task must have an owner
And, trying with the -d (debug) option, in order to get the Python call stack: $ koji -d build dist-6E-epel 'cvs:// cvs.fedoraproject.org/cvs/pkgs?rpms/R-msm/EL-6#R-msm-0_9_1-2_el6' successfully connected to hub Traceback (most recent call last): File "/usr/bin/koji", line 5077, in <module> rv = locals()[command].__call__(options, session, args) File "/usr/bin/koji", line 796, in handle_build task_id = session.build(source, target, opts, priority=priority) File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 1468, in __call__ return self.__func(self.__name,args,opts) File "/usr/lib/python2.6/site-packages/koji/__init__.py", line 1718, in _callMethod raise err koji.GenericError: task must have an owner
Note that I have imported the CVS-checkout package with 'fedora-cvs R-msm', and that all went well.
If you have any idea, do not hesitate.
Regards
Denis
packaging@lists.fedoraproject.org