Description of problem: Traceback occurred when fedora-package could not access to admin.fedoraproject.org. Failure to access url should be handled gracefully. Version-Release number of selected component: fedora-packager-0.5.10.1-1.fc18 Additional info: cmdline: /usr/bin/python /usr/bin/fedora-packager-setup executable: /usr/bin/fedora-packager-setup kernel: 3.6.10-5.fc18.x86_64 uid: 1000 Truncated backtrace: proxyclient.py:396:send_request:error: (6, 'Could not resolve host: admin.fedoraproject.org; Name or service not known') Traceback (most recent call last): File "/usr/bin/fedora-packager-setup", line 108, in <module> main() File "/usr/bin/fedora-packager-setup", line 92, in main fedora_cert.create_user_cert(username) File "/usr/lib/python2.7/site-packages/fedora_cert/__init__.py", line 97, in create_user_cert fas.logout() File "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py", line 261, in logout self.send_request('logout', auth=True) File "/usr/lib/python2.7/site-packages/fedora/client/baseclient.py", line 344, in send_request auth_params=auth_params, retries=retries) File "/usr/lib/python2.7/site-packages/fedora/client/proxyclient.py", line 396, in send_request request.perform() error: (6, 'Could not resolve host: admin.fedoraproject.org; Name or service not known') Local variables in innermost frame: username: 'luya' retries: 0 req_params: None i: ('_csrf_token', '6991d847c8aa87216e31d897d5bbc21665fba6a8') self: <fedora.client.fas2.AccountSystem object at 0x11f81d0> request: <pycurl.Curl object at 0x12cfaf0> session_id: '480346bd7e4a715aec6160aa4b1c65a02426bc68' req_data: 'user_name=luya&login=Login&password=F288gto16v&_csrf_token=6991d847c8aa87216e31d897d5bbc21665fba6a8' auth_params: {'username': 'luya', 'password': 'F288gto16v', 'session_id': '480346bd7e4a715aec6160aa4b1c65a02426bc68'} headers: ['User-agent: Fedora Account System Client/0.3.29', 'Accept: application/json', 'Expect:'] token: <sha1 HASH object @ 0x125c620> num_tries: 0 complete_params: {'user_name': 'luya', 'login': 'Login', 'password': 'F288gto16v', '_csrf_token': '6991d847c8aa87216e31d897d5bbc21665fba6a8'} url: 'https://admin.fedoraproject.org/accounts/logout' file_params: None method: 'logout' password: 'F288gto16v' data: None response: <fedora.client.proxyclient._PyCurlData object at 0x1265f50>
Created attachment 665101 [details] File: backtrace
Created attachment 665102 [details] File: core_backtrace
Created attachment 665103 [details] File: dso_list
Created attachment 665104 [details] File: environ
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.