Bug 823439

Summary:	Subscription-manager unsubscribe --all throws 'int' object is unsubscriptable
Product:	Red Hat Enterprise Linux 5	Reporter:	Shwetha Kallesh <skallesh>
Component:	subscription-manager	Assignee:	William Poteat <wpoteat>
Status:	CLOSED NOTABUG	QA Contact:	Entitlement Bugs <entitlement-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.9	CC:	alikins, dgoodwin, jmolet, jsefler, spandey
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-25 14:21:53 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:	771748

Description Shwetha Kallesh 2012-05-21 09:41:47 UTC

Description of problem:
Subscription-manager unsubscribe --all throws 'int' object is unsubscriptable 

Version-Release number of selected component (if applicable):

[root@dhcp201-196 ~]# rpm -qa | grep subscription-manager
subscription-manager-gnome-1.0.2-1.git.2.2b23e6e.el6.x86_64
subscription-manager-migration-1.0.2-1.git.2.2b23e6e.el6.x86_64
subscription-manager-migration-data-1.12.1.8-1.git.0.c91a246.el6.noarch
subscription-manager-firstboot-1.0.2-1.git.2.2b23e6e.el6.x86_64
subscription-manager-1.0.2-1.git.2.2b23e6e.el6.x86_64


How reproducible:


Steps to Reproduce:
1.subscription-manager register --org=admin --user=admin --password=admin
2.subscription-manager subscribe --pool=8ac149343730a547013730a5f10603ac --pool=8ac149343730a547013730a5ed260239
3.subscription-manager unsubscribe --all
  
Actual results:
'int' object is unsubscriptable

Expected results:
Should unsubscribe all from all subscriptions

Additional info:

Comment 3 Devan Goodwin 2012-05-25 14:21:53 UTC

This was caused by running against a development candlepin deploy from within a very specific timeframe where that call returned an int instead of nothing (old) and JSON (new). The client you were using was expecting the new json. Candlepin within this narrow window should not have been deployed.

Closing as per the duplicate bug for 6.3: #823438