Description of problem:Échec du téléversement du uReport au serveur « https://retrace.fedoraproject.org/faf » avec curl : Could not resolve host: retrace.fedoraproject.org Erreur : curl_easy_perform: Couldn't resolve host name (« report_uReport » a quitté avec code retour 1) Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1699938 [details] abrt-server Could not resolve host: retrace.fedoraproject.org and kwalletd5 crashes concerns also 185356 kwalletd5 killed by SIGABRT occurs 70 in one day
Created attachment 1699939 [details] jounalctl generated concerns also kwalletd5 killed by SIGABRT occurs 70 in one day
This is known issue. The server is down due the datacenter move. See https://status.fedoraproject.org/ Unfortunatelly, this will take up to two more weeks. :(
*** Bug 1850998 has been marked as a duplicate of this bug. ***
*** Bug 1849546 has been marked as a duplicate of this bug. ***
And any workaround? Honestly how can comunity report bugs if the ABRT is down. Wow - I am astonished by the fact that you dont even care. Yeah cool - lets move the servers for few weeks. Nothing will happen, right? As a QA I find this at this time completely unacceptable to have some service at 100% down status even for a day, not to mention month or two.
Also - how is it possible that this bug is the is closed as CANTFIX and bug 1849546 that is the original one is closed as duplicate. It seeems that you have not only problems with your products (every software has bugs) but also with the processes on how to handle bugs/issues/stories etc.
this is still not working, why?
I*m guessing related to https://pagure.io/fedora-infrastructure/issue/9060