Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 595723 - Not able to unsubscribe multiple product at a time
Not able to unsubscribe multiple product at a time
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Bryan Kearney
wes hayutin
Depends On:
Blocks: 568421
  Show dependency treegraph
Reported: 2010-05-25 09:12 EDT by spandey
Modified: 2015-04-23 19:56 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-05-19 09:37:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2011:0611 normal SHIPPED_LIVE new package: subscription-manager 2011-05-18 13:56:21 EDT

  None (edit)
Description spandey 2010-05-25 09:12:59 EDT
Description of problem:

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

How reproducible:

Candlepin : sachtest.usersys.redhat.com
client : Rhel 6 with SM vsersion 60

Steps to Repro : 
Login to the Client with valid credentails 
subscribed for multiple product 
Try to unsubscribe multiple entitlement at a time executing following command 

subscription-manager-cli unsubscribe –serial=13 –serial=14 --serial=15

 Expected Result : 
we should have process to unsubscribe multiple entitlement at a time 
we can use “unsubscribe” option but it will unsubscribe all entitlement 
suppose i want to have some entitlement on my machine and  remove some of them 
so it will take more manual efforts 

Actual Result : 
Only the last mentioned subscription has been unsubscribed (--serial=15)
Multiple unsubscribe is not working  

Note : If you think i am executing invalid scenario please close this defect
Comment 2 wes hayutin 2010-05-27 15:39:34 EDT
please retest once the next subscription-manager version 61 is released
Comment 3 RHEL Product and Program Management 2010-06-07 11:53:54 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
Comment 6 spandey 2010-07-14 09:30:39 EDT
Again i am able to repro defect 

SM version : 67
candlepin : IT Env (Candlepin1)

[root@sachrhel6 facts]# subscription-manager-cli unsubscribe --serial=322 --serial=321
[root@sachrhel6 facts]# subscription-manager-cli list --consumed+-------------------------------------------+
    Consumed Product Subscriptions

Name:               	Red Hat Enterprise Linux Advanced Platform
ContractNumber:       	1632092                  
SerialNumber:       	322                      
Active:             	True                     
Begins:             	2009-05-12               
Expires:            	2010-12-31               

[root@sachrhel6 facts]# 

using above step it removes only serial number "321 "
Comment 7 Ajay Kumar Nadathur Sreenivasan 2010-08-24 11:34:23 EDT
  Can you please attach the logs? I am sure subscription-manager must have faced some internal exception..
Comment 8 spandey 2010-09-08 08:32:01 EDT
I got confirmation from prad 

unsubscribe design is to unsubscribe only one serial number at a time 

same like unsubscribe option in GUI

So i am resolving defect as verified
Comment 10 errata-xmlrpc 2011-05-19 09:37:03 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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