amount of reports by abrt

I attended a talk about abrt and noticed there are good number of reports [1] generated by issues in ovirt. Thanks, Piotr [1] https://retrace.fedoraproject.org/faf/reports/

On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski <piotr.kliczewski@gmail.com> wrote:
I attended a talk about abrt and noticed there are good number of reports [1] generated by issues in ovirt.
Did they teach how to read these reports? Can you tell what is the 10 most common exceptions occurring in oVirt context?
Thanks, Piotr
[1] https://retrace.fedoraproject.org/faf/reports/ _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EECX2SVR4Q4TG4...

niedz., 11 lis 2018, 09:16: Dan Kenigsberg <danken@redhat.com> napisał(a):
On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski <piotr.kliczewski@gmail.com> wrote:
I attended a talk about abrt and noticed there are good number of
reports [1] generated by issues in ovirt.
Did they teach how to read these reports? Can you tell what is the 10 most common exceptions occurring in oVirt context?
Yes, please take a look at [1]. There are good numbers of reports for ovirt components some with many millions occurrances over several years.
Thanks, Piotr
[1] https://retrace.fedoraproject.org/faf/reports/ _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/EECX2SVR4Q4TG4...

On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski <piotr.kliczewski@gmail.com> wrote:
I attended a talk about abrt and noticed there are good number of reports [1] generated by issues in ovirt.
Interesting, but does not seem very useful now. For example this issue: https://retrace.fedoraproject.org/faf/reports/1800689/ https://retrace.fedoraproject.org/faf/problems/bthash/?bth=78aadb337727a80e425738f897ce652408ee396d&bth=f9f894ff896f63455df6175635c7ec441cab225 11103922 reports for ovirt-imageio-daemon 1.0.0 6501 repots for ovirt-imageio-daemon 1.1.0 But there is no info about this error, except the name of the exception NoSectionError Which means code tried to access non-existing section in a config file. The current version of imageio is 1.4.5, and the version released with 4.2.0 was 1.3 or 1.4, so this whatever this issue was, it is not relevant for long time. This could be more relevant if we could get mail about reports when they are submitted to the system. Do you know how we can configure the system to make the reports more useful? Nir

niedz., 11 lis 2018, 15:26: Nir Soffer <nsoffer@redhat.com> napisał(a):
On Sat, Nov 10, 2018 at 8:19 PM Piotr Kliczewski < piotr.kliczewski@gmail.com> wrote:
I attended a talk about abrt and noticed there are good number of reports [1] generated by issues in ovirt.
Interesting, but does not seem very useful now.
For example this issue: https://retrace.fedoraproject.org/faf/reports/1800689/
11103922 reports for ovirt-imageio-daemon 1.0.0 6501 repots for ovirt-imageio-daemon 1.1.0
But there is no info about this error, except the name of the exception NoSectionError Which means code tried to access non-existing section in a config file.
The current version of imageio is 1.4.5, and the version released with 4.2.0 was 1.3 or 1.4, so this whatever this issue was, it is not relevant for long time.
This could be more relevant if we could get mail about reports when they are submitted to the system. Do you know how we can configure the system to make the reports more useful?
Not sure but will ask about email notifications and if there is a way to remove old, not vaild reports.
Nir
participants (3)
-
Dan Kenigsberg
-
Nir Soffer
-
Piotr Kliczewski