Bug 683550 - Version number isn't parsed right for installed products
Summary: Version number isn't parsed right for installed products
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python-rhsm
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Devan Goodwin
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 568421
TreeView+ depends on / blocked
 
Reported: 2011-03-09 17:02 UTC by J.C. Molet
Modified: 2013-01-10 10:51 UTC (History)
3 users (show)

Fixed In Version: python-rhsm-0.95.5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:35:24 UTC
Target Upstream Version:


Attachments (Terms of Use)
version parsing (87.51 KB, image/png)
2011-03-09 17:02 UTC, J.C. Molet
no flags Details
working version number (141.34 KB, image/png)
2011-03-29 16:20 UTC, J.C. Molet
no flags Details
pem used (2.07 KB, application/x-x509-ca-cert)
2011-03-29 16:22 UTC, J.C. Molet
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0608 0 normal SHIPPED_LIVE new package: python-rhsm 2011-05-18 17:56:26 UTC

Description J.C. Molet 2011-03-09 17:02:30 UTC
Created attachment 483264 [details]
version parsing

Description of problem:
In subscription-manager-gui on the "My Installed Software" tab, it doesn't look like the version field is being parsed right.  It shows an unformatted OID number.

Version-Release number of selected component (if applicable):
subscription-manager-gnome-0.95.4-1.git.1.bb03d4e.el6.x86_64

Steps to Reproduce:
1. Install subscription-manager-gnome on a rhel6 machine.
2. On your on premise candlepin, import all test data.
3. Copy the "Red Hat Enterprise Linux Entitlement" product cert to your client's cert folder.
4. run the gui and go to the my installed software tab.
  
Actual results:
you see an unformatted version number.

Expected results:
You see something more human readable

Additional info:
see the attached screen shot.

Comment 1 James Bowes 2011-03-10 13:03:01 UTC
Certificate parsing doesn't seems to fail whenever there's an extension present with an empty value. I'm working on a fix to the extension parsing now, but the current setup reads the cert as text, then parses the output. We'd be much better served by doing it via some api (python-nss?)

Comment 2 James Bowes 2011-03-11 16:05:14 UTC
fixed in master and RHEL6 branches. should be available in python-rhsm-0.95.5

Comment 7 J.C. Molet 2011-03-29 16:20:34 UTC
Created attachment 488493 [details]
working version number

This verifies that the bug is now fixed.

Comment 8 J.C. Molet 2011-03-29 16:22:08 UTC
Created attachment 488495 [details]
pem used

This cert file was the one used to reproduce and verify the bug.  Its useful because it has blank values for the version.

Comment 9 errata-xmlrpc 2011-05-19 13:35:24 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0608.html


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