Bug 725857

Summary: reinstate getVersion_fromProduct and getProduct_fromPRODUCT in python bindings
Product: Red Hat Enterprise Linux 6 Reporter: Jiri Moskovcak <jmoskovc>
Component: libreportAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: dfediuck, mnowak, ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: libreport-2.0.5-3.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 12:14:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 705274    
Attachments:
Description Flags
Proposed (tested) patch none

Description Jiri Moskovcak 2011-07-26 18:43:51 UTC 
Description of problem:
Anaconda doesn't have /etc/*-release (why?) so libreport can't use it to determine product and version and fails to report a problem. We need to reinstate the  getVersion_fromProduct and getProduct_fromPRODUCT from the report package which can get the required release information directly from anaconda.

Version-Release number of selected component (if applicable):
libreport-2.0.5-2.el6

How reproducible:
100%

Steps to Reproduce:
1. create anaconda image with libreport packages
2. make anaconda crash

  
Actual results:
libreport fails to determine release -> bz and rhtsupport plugins fails to create a ticket.
Comment 2 Jiri Moskovcak 2011-07-28 14:14:16 UTC 
Created attachment 515728 [details]
Proposed (tested) patch

This patch fixes the problem with missing /etc/*-release on Anaconda images. It uses the same method to determine the os release as report.
Comment 6 errata-xmlrpc 2011-12-06 12:14:17 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.

http://rhn.redhat.com/errata/RHBA-2011-1598.html