RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1257159 - abrt-cli allows to start reporting not-reportable problems
Summary: abrt-cli allows to start reporting not-reportable problems
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: abrt
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: abrt
QA Contact: Martin Kyral
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-26 11:43 UTC by Martin Kyral
Modified: 2017-08-01 18:15 UTC (History)
3 users (show)

Fixed In Version: abrt-2.1.11-48.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 18:15:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Patch 1/3: reportclient: fix verbosity test (961 bytes, patch)
2017-02-14 12:07 UTC, Matej Habrnal
no flags Details | Diff
Patch 2/3: tree-wide: introduce 'stop_on_not_reportable' option (10.57 KB, patch)
2017-02-14 12:07 UTC, Matej Habrnal
no flags Details | Diff
Patch 3/3: reportclient: honor ABRT_VERBOSE (3.65 KB, patch)
2017-02-14 12:07 UTC, Matej Habrnal
no flags Details | Diff
Patch 1/5: lib: stop printing out a debug message 'adding: ' (889 bytes, patch)
2017-02-14 12:44 UTC, Matej Habrnal
no flags Details | Diff
Patch 2/5: cli: don't start reporting of not-reportable problems (1.41 KB, patch)
2017-02-14 12:44 UTC, Matej Habrnal
no flags Details | Diff
Patch 3/5: cli: introduce unsafe reporting for not-reporable problems (8.93 KB, patch)
2017-02-14 12:44 UTC, Matej Habrnal
no flags Details | Diff
Patch 4/5: cli: configure libreport to ignore not-reportable (1.52 KB, patch)
2017-02-14 12:44 UTC, Matej Habrnal
no flags Details | Diff
Patch 5/5: cli: print out the not-reportable reason (1.42 KB, patch)
2017-02-14 12:44 UTC, Matej Habrnal
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Github abrt abrt issues 986 0 None None None Never
Red Hat Product Errata RHBA-2017:1927 0 normal SHIPPED_LIVE abrt, abrt-java-connector, libreport bug fix update 2017-08-01 18:07:39 UTC

Description Martin Kyral 2015-08-26 11:43:49 UTC
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):
abrt-2.1.11-31.el7

How reproducible:
Always

Steps to Reproduce:
1. run the upstream test or repeat the reproducing steps (see above)
2.
3.

Comment 2 Matej Habrnal 2017-01-26 12:58:17 UTC
Opened upstream pull requests:
https://github.com/abrt/abrt/pull/1221
https://github.com/abrt/libreport/pull/475

Comment 4 Matej Habrnal 2017-02-14 12:07:07 UTC
Created attachment 1250191 [details]
Patch 1/3: reportclient: fix verbosity test

Comment 5 Matej Habrnal 2017-02-14 12:07:10 UTC
Created attachment 1250192 [details]
Patch 2/3: tree-wide: introduce 'stop_on_not_reportable' option

Comment 6 Matej Habrnal 2017-02-14 12:07:13 UTC
Created attachment 1250193 [details]
Patch 3/3: reportclient: honor ABRT_VERBOSE

Comment 7 Matej Habrnal 2017-02-14 12:44:46 UTC
Created attachment 1250219 [details]
Patch 1/5: lib: stop printing out a debug message 'adding: '

Comment 8 Matej Habrnal 2017-02-14 12:44:49 UTC
Created attachment 1250220 [details]
Patch 2/5: cli: don't start reporting of not-reportable problems

Comment 9 Matej Habrnal 2017-02-14 12:44:52 UTC
Created attachment 1250221 [details]
Patch 3/5: cli: introduce unsafe reporting for not-reporable problems

Comment 10 Matej Habrnal 2017-02-14 12:44:55 UTC
Created attachment 1250222 [details]
Patch 4/5: cli: configure libreport to ignore not-reportable

Comment 11 Matej Habrnal 2017-02-14 12:44:57 UTC
Created attachment 1250223 [details]
Patch 5/5: cli: print out the not-reportable reason

Comment 13 errata-xmlrpc 2017-08-01 18:15:18 UTC
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.

https://access.redhat.com/errata/RHBA-2017:1927


Note You need to log in before you can comment on or make changes to this bug.