#61 Enable system wide ABRT autoreporting
Closed: Fixed 3 years ago by lruzicka. Opened 6 years ago by msuchy.

By default ABRT is only enabled per user. And not system wide. It poped up during
https://bugzilla.redhat.com/show_bug.cgi?id=1469813
where ABRT was unable to report it because Gnome did not start at all.

It will be nice, if QA can enable ABRT autoreporting using command:
abrt-auto-reporting 1
This way ABRT will send micro reports (without environment and any other sensitive data) to retrace.fedoraproject.org/faf/ for any crash that happened in system. Without any human intervention.


well, it's a bit tricky to just slide this kind of environment modification into all tests without potentially invalidating the test - we have to find an appropriate point to do it. but we may be able to do it for at least some cases, we'll try and look at it.

in general the intent of the openQA tests is to test the system as we ship it.

I advised @msuchy to file a ticket here. I agree that we want to test the unmodified system, on the other hand starting one extra service which automatically sends crash reports (and which most probably can't be enabled by default due to privacy concerns) could be very useful when running regular automated tests, and hopefully will not affect anything else. I think there's a good opportunity here to detect new crashes early with little to no impact to the system under test.

Metadata Update from @adamwill:
- Issue priority set to: Low

6 years ago

Metadata Update from @adamwill:
- Issue tagged with: improvetest

6 years ago

Metadata Update from @lruzicka:
- Issue assigned to lruzicka

5 years ago

What if we created a special Medium Type, for example Fedora ABRT, where some of the tests would run with this switched on, for example those intented for Workstation-live-iso, and perhaps also Server-dvd-iso?
The question is, where do I switch the automatic reporting on ... on boot prompt? After installation?

I suppose we could look at doing it around here - as you can see, recently I've had to invent two icky 'mess around with the installed system after the install completes' bits, so why would another hurt :(

we could just have a variable which makes the test go to a console there and do chroot /mnt/sysimage; abrt-auto-reporting 1, or so. It's ugly, but meh.

This functionality has been added to our test cases, see PR #98 .

This was merged a long time ago.

Metadata Update from @lruzicka:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata