Red Hat Bugzilla – Bug 1257159
abrt-cli allows to start reporting not-reportable problems
Last modified: 2017-08-01 14:15:18 EDT
Description of problem:
The upstream cli-sanity test fails in the not-reportable phase as follows:
:: [ BEGIN ] :: Running 'touch /var/spool/abrt/ccpp-2015-08-21-19:08:55-7279/not-reportable'
:: [ PASS ] :: Command 'touch /var/spool/abrt/ccpp-2015-08-21-19:08:55-7279/not-reportable' (Expected 0, got 0)
:: [ BEGIN ] :: Running 'abrt-cli report /var/spool/abrt/ccpp-2015-08-21-19:08:55-7279 2>&1 | tee abrt-cli-report-not-reportable.log'
Error: no processing is specified for event 'report-cli'
:: [ PASS ] :: Command 'abrt-cli report /var/spool/abrt/ccpp-2015-08-21-19:08:55-7279 2>&1 | tee abrt-cli-report-not-reportable.log' (Expected 0, got 0)
:: [ FAIL ] :: File 'abrt-cli-report-not-reportable.log' should contain 'Problem '/var/spool/abrt/ccpp-2015-08-21-19:08:55-7279' cannot be reported'
because abrt-cli report does not print the '... cannot be reported' message out.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run the upstream test or repeat the reproducing steps (see above)
Opened upstream pull requests:
Created attachment 1250191 [details]
Patch 1/3: reportclient: fix verbosity test
Created attachment 1250192 [details]
Patch 2/3: tree-wide: introduce 'stop_on_not_reportable' option
Created attachment 1250193 [details]
Patch 3/3: reportclient: honor ABRT_VERBOSE
Created attachment 1250219 [details]
Patch 1/5: lib: stop printing out a debug message 'adding: '
Created attachment 1250220 [details]
Patch 2/5: cli: don't start reporting of not-reportable problems
Created attachment 1250221 [details]
Patch 3/5: cli: introduce unsafe reporting for not-reporable problems
Created attachment 1250222 [details]
Patch 4/5: cli: configure libreport to ignore not-reportable
Created attachment 1250223 [details]
Patch 5/5: cli: print out the not-reportable reason
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.