Bug 812383

Summary:	Subscription-manager autosubscription feedback
Product:	Red Hat Enterprise Linux 5	Reporter:	Matt Reid <mreid>
Component:	subscription-manager	Assignee:	Alex Wood <awood>
Status:	CLOSED WORKSFORME	QA Contact:	Entitlement Bugs <entitlement-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.9	CC:	awood, bkearney
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-05-03 15:30:01 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:
Bug Depends On:
Bug Blocks:	771748

Description Matt Reid 2012-04-13 14:48:47 UTC

Description of problem:
Currently, when I autosubscribe using the cli, the system doesn't tell me all of the information I care to know when it picks something for me. 

Version-Release number of selected component (if applicable):
subscription-manager-1.0.0-1.git.19.46c8d80

Steps to Reproduce:
1a. Subscription-manager subscribe --auto
or
1b. Subscription-manager register --auto
  
Actual results:
# Subscription-manager subscribe --auto
Installed Product Current Status:
Product Name:  Awesome OS Server Bits
Status: Subscribed

Expected results:
If I had autosubscribed, it might be useful to know what my SLA is now. If they did an autosubscribe specifying an SLA to use, I think it would be good reinforcement to see that listed out, letting them know we listened to them without them having to doublecheck our work on their own.

If there's a way where they could end up being subscribed to an org they didn't pick themselves, we should list that as well, but I don't think that can happen. Please correct me if I'm mistaken.

I'd like to see something like:
# Subscription-manager subscribe --auto
Installed Product Current Status:
Product Name:  Awesome OS Server Bits
Status: Subscribed
Service Level: Standard

Comment 1 RHEL Program Management 2012-04-17 02:08:43 UTC

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 2 Alex Wood 2012-05-03 15:30:01 UTC

Matt,

The SLA is printed out during an auto-subscription, but only if an SLA is specified.

For example:

[root@rhel-6-2-812383 subscription-manager]# PYTHONPATH=./src/:../python-rhsm/src/ src/subscription-manager subscribe --auto --servicelevel="Standard"
Service level set to: Standard
Installed Product Current Status:
Product Name:           Awesome OS for x86_64 Bits
Status:                 Not Subscribed           

Product Name:           Red Hat Enterprise Linux Workstation
Status:                 Not Subscribed           

I'm going to close this since I believe the behavior already provides the functionality you want.  Please reopen if you disagree.

Comment 3 Matt Reid 2012-05-04 20:29:00 UTC

(In reply to comment #2)
> Matt,
> 
> The SLA is printed out during an auto-subscription, but only if an SLA is
> specified.
> 
> For example:
> 
> [root@rhel-6-2-812383 subscription-manager]#
> PYTHONPATH=./src/:../python-rhsm/src/ src/subscription-manager subscribe --auto
> --servicelevel="Standard"
> Service level set to: Standard
> Installed Product Current Status:
> Product Name:           Awesome OS for x86_64 Bits
> Status:                 Not Subscribed           
> 
> Product Name:           Red Hat Enterprise Linux Workstation
> Status:                 Not Subscribed           
> 
> I'm going to close this since I believe the behavior already provides the
> functionality you want.  Please reopen if you disagree.

Awesome, that's most of what I was looking for.

I think we may want to print out SLA when they auto-subscribe and don't specify an SLA though. As my understanding is whatever that picks will become their SLA preference for the future.