Bug 997120 - Subscribing a client to SAM server classifies it as invalid subscription (RED) vs. insufficient subscription (YELLOW)
Summary: Subscribing a client to SAM server classifies it as invalid subscription (RED...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Subscription Asset Manager
Classification: Retired
Component: candlepin
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Katello Bug Bin
QA Contact: SAM QE List
URL:
Whiteboard:
Depends On:
Blocks: sam13-tracker
TreeView+ depends on / blocked
 
Reported: 2013-08-14 17:52 UTC by sthirugn@redhat.com
Modified: 2013-08-15 16:26 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-15 16:25:32 UTC
Embargoed:


Attachments (Terms of Use)

Description sthirugn@redhat.com 2013-08-14 17:52:06 UTC
Description of problem:
Subscribing a client to SAM server classifies it as invalid subscription (RED) vs. insufficient subscription (YELLOW)

Version-Release number of selected component (if applicable):
* candlepin-0.8.19-1.el6sam.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.8.19-1.el6sam.noarch
* candlepin-tomcat6-0.8.19-1.el6sam.noarch
* elasticsearch-0.19.9-8.el6sat.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.4.2-2.el6sat.noarch
* katello-cli-1.4.3-4.el6sat.noarch
* katello-cli-common-1.4.3-4.el6sat.noarch
* katello-common-1.4.3-5.el6sam_splice.noarch
* katello-configure-1.4.4-2.el6sat.noarch
* katello-glue-candlepin-1.4.3-5.el6sam_splice.noarch
* katello-glue-elasticsearch-1.4.3-5.el6sam_splice.noarch
* katello-headpin-1.4.3-5.el6sam_splice.noarch
* katello-headpin-all-1.4.3-5.el6sam_splice.noarch
* katello-selinux-1.4.4-2.el6sat.noarch
* thumbslug-0.0.32-1.el6sam.noarch
* thumbslug-selinux-0.0.32-1.el6sam.noarch

Subscription-Manger version: subscription-manager-1.1.23-1.el6.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Install SAM
2. Import a manifest with a subscription having a product with limit of 16 cores
3. Register and subscribe a client with 24 cores
subscription-manager register --username $user --password $pass --org $org --autosubscribe --force


Actual results:
The SAM GUI shows the client as RED (Invalid Subscription) vs. YELLOW (Insufficient subscription)

UI Details showed:
JBoss Enterprise Application Platform 	Not covered by a valid subscription. 

Expected results:
The SAM GUI should show the client as YELLOW (Insufficient subscription)

Additional info:
1. Running Auto-attach available subscriptions to all systems didnt fix the problem also.
2. I went ahead and manually attached the subscriptions in SAM GUI.  Then the compliance turned to YELLOW - Insufficient.

UI Details Showed:
JBoss Enterprise Application Platform with Management, 16 Core Standard, L3 Support Partner 	Only covers 16 of 24 cores.

Comment 1 Carter Kozak 2013-08-14 18:56:08 UTC
I think the problem here is that no entitlements are being attached, correct?

Comment 2 sthirugn@redhat.com 2013-08-14 20:35:12 UTC
@Carter: Correct.  Auto subscribe is not making the client yellow.  Instead it stays in red.

Comment 3 Carter Kozak 2013-08-15 15:06:47 UTC
I don't think we garuntee that auto-attach will bind subscriptions that aren't going to be fully compliant at this point.  In the next couple weeks we might introduce some code that only attaches subscriptions that can fully cover a product.

I think it's safe to close this as not a bug.

Comment 4 sthirugn@redhat.com 2013-08-15 16:26:11 UTC
Closing the issue as NOTABUG as per Carter's Comment 3 above.


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