Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 888866

Summary: [RFE] Customers should be able to use subscriptions with new attributes on old clients
Product: [Community] Candlepin (Migrated to Jira) Reporter: Amanda Carter <acarter>
Component: candlepinAssignee: Carter Kozak <ckozak>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 0.9CC: acarter, aflierl, bkearney, ckozak, fdacunha, ftan, jsefler, liliu, omaciel, pdemmers, pep, pmutha, ppatanka, sauchter, soliu, xdmoon, yjog
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-23 15:50:04 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: 840995    

Description Amanda Carter 2012-12-19 16:49:56 UTC 
Description of problem:

In our current state, we prevent users for accessing a subscription with an attribute that we can't enforce until they upgrade to a version of the client that supports that attribute. We message to them that using it can't be supported and they should upgrade. (Adding RAM & Cores for example)

Instead, we should err on the side of being permissive; message to the user that they should upgrade in order to be able to report compliance status, but still permit usage. 

Would it be possible or even desirable to reflect this status in status messaging on the machine? So that perhaps another yellow status could tell a user that we aren't sure and they should upgrade (or something like that)?
Comment 2 Carter Kozak 2013-07-01 18:02:54 UTC 
commit 779ba5ba60700b0d03f534e3658ae2c6b97ffe58
Author: ckozak <ckozak>
Date:   Tue Jun 25 13:11:56 2013 -0400

    888866: Old sm can use subs with new attributes
Comment 6 Bryan Kearney 2013-08-01 15:55:13 UTC 
Moving these to ON_QA. The tooling must have missed moving these.
Comment 9 Liu Song 2013-08-05 08:52:38 UTC 
Hi,

I verify the issue using all of the skus in doc-95917, and all the skus in the doc no matter openshift skus or JBoss skus have no the issue exist now.

Please re-open the bug if anyone found the issue still exist using some skus in the future, thanks!

https://docspace.corp.redhat.com/docs/DOC-95917

Regards
song
Comment 21 Bryan Kearney 2013-10-01 14:12:34 UTC 
Released with 5.10