Bug 768506

Summary:	Remove flex expiry code from client side
Product:	Red Hat Enterprise Linux 5	Reporter:	Chris Duryee <cduryee>
Component:	python-rhsm	Assignee:	Bryan Kearney <bkearney>
Status:	CLOSED ERRATA	QA Contact:	Entitlement Bugs <entitlement-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.8	CC:	bkearney, jsefler, wpoteat
Target Milestone:	rc
Target Release:	5.8
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	No Description Needed	Story Points:	---
Clone Of:	754425	Environment:
Last Closed:	2012-02-21 06:44:37 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:	754425
Bug Blocks:	715031

Description Chris Duryee 2011-12-16 20:35:49 UTC

bug for making same change in python-rhsm.

QE note: I don't think this is testable, except to confirm that all existing tests pass. The BZ is for removal of unused code.

+++ This bug was initially created as a clone of Bug #754425 +++

The code related to flex expiry is gone from the server (mostly). Remove it from the client, as well.

--- Additional comment from bkearney on 2011-11-17 17:25:09 EST ---

*** Bug 754426 has been marked as a duplicate of this bug. ***

Comment 1 Chris Duryee 2011-12-16 20:36:46 UTC

08aaa595bb8cdbf59fba3bd70cad4fd26f88166e master 0.99.1
cb21f64f8cf01a903e8143ac288a70fedb4ccd05 RHEL5.8 0.98.7

Comment 2 John Sefler 2011-12-20 17:42:05 UTC

moving to VERIFIED based on https://bugzilla.redhat.com/show_bug.cgi?id=754425#c5

Comment 3 William Poteat 2012-01-27 14:24:06 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No Description Needed

Comment 4 errata-xmlrpc 2012-02-21 06:44:37 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-2012-0280.html