Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1368460

Summary: do not use deprecated rs/problems in reporter-rhtsupport
Product: Red Hat Enterprise Linux 8 Reporter: Matej Habrnal <mhabrnal>
Component: libreportAssignee: abrt <abrt-devel-list>
Status: CLOSED WONTFIX QA Contact: CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity: unspecified Docs Contact:
Priority: high    
Version: 8.4CC: mkyral, msuchy
Target Milestone: rcKeywords: Triaged
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1368472 (view as bug list) Environment:
Last Closed: 2020-11-01 03:03:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1368472    

Description Matej Habrnal 2016-08-19 13:20:21 UTC
Description of problem:
reporter-rhtsupport uses rs/problems when it checks for "hints" (known solutions for the problem, making it unnecessary for user to create tickets). 

As it is said in comments in [1] rs/problems is deprecated and reporter-rhtsupport should use rs/recommendations instead. We currently don't know what kind of information we should send to rs/recommendations, it has to be figured out in [1].

Additional info:
We've started to upload whole abrt's dump directories to the support cases (#1261358) and the uploaded data has bigger size then is allowed so the checks for "hints" functionality is not executed now. The size limitation of uploaded data is because we don't want to upload such a big data twice (#846203). 

[1] https://projects.engineering.redhat.com/browse/CPSTRATA-79

Comment 1 Matej Habrnal 2016-08-19 13:34:01 UTC
See also Strata API Curl Examples https://mojo.redhat.com/docs/DOC-75710#jive_content_id_Problems_Ask_Shadowman

Comment 3 Matej Habrnal 2018-06-19 12:38:33 UTC
We've reopened a related ticket to this issue [1] and we are waiting for a response there.

I suggest resolving this bugzilla in next RHEL7 release.

[1] https://projects.engineering.redhat.com/browse/CPSTRATA-79

Comment 6 ekulik 2020-02-13 10:08:01 UTC
Seems hopeless to get any response from the Strata/Hydra/whatever people, so we should probably just dump the code and figure something else out eventually.

Comment 9 RHEL Program Management 2020-11-01 03:03:03 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.