On Wed, Apr 19, 2017 at 4:43 PM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote:
Hi, I posted the new integration [1] to 4.1 -
https://gerrit.ovirt.org/#/
q/topic:backport-abrt-intgr for review.
The DocText says:
Result:
ABRT service is now running on each Hypervisor and exposes crash report as
part of vdsm sos output.
Why vdsm sos plugins is taking care of abrt report exposure?
sos 3.4 has abrt plugin with the possiblity to provide detailed info.
Has vdsm sos plugin been tested with sos 3.4 at all?
Abrt is a service that runs in parallel to vdsm and collect binaries
and
python crashes under /var/run/tmp - to try that out you can crash a qemu
process or vdsm with signal -6 and watch the report using "abrt-cli list"
command, which its output will be reported by our sos plugin.
Thanks,
Yaniv Bronhaim.
[1]
https://bugzilla.redhat.com/show_bug.cgi?id=917062
--
Yaniv Bronhaim.
_______________________________________________
Devel mailing list
Devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
--
SANDRO BONAZZOLA
ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D
Red Hat EMEA <
https://www.redhat.com/>
<
https://red.ht/sig>
TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>