Bug 757978 - unsubscribe --all, works even though the client is not registered
Summary: unsubscribe --all, works even though the client is not registered
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: William Poteat
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 771748
TreeView+ depends on / blocked
 
Reported: 2011-11-29 05:33 UTC by Shwetha Kallesh
Modified: 2012-06-05 12:56 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-05 12:55:41 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Shwetha Kallesh 2011-11-29 05:33:19 UTC
Description of problem:

unsubscribe --all, works even though the client is not registered

Version-Release number of selected component (if applicable):
[root@tiger ~]# rpm -qa | grep subscription-manager
subscription-manager-firstboot-0.98.3-1.el5
subscription-manager-0.98.3-1.el5
subscription-manager-gnome-0.98.3-1.el5
subscription-manager-debuginfo-0.98.3-1.el5
subscription-manager-migration-0.98.3-1.el5


How reproducible:


Steps to Reproduce:
1.unregister the client
2.execute subscription-manager unsubscribe --all
3.
  
Actual results:

This machine has been unsubscribed from all subscriptions

Expected results:

should say "Error: You need to register this system by running `register` command before using this option"


Additional info:

Comment 1 Devan Goodwin 2012-06-05 12:55:41 UTC
Unsubscribe can actually be used for the "offline" use case, where the system is not registered, and the user is manually importing their certificates. As such they need to be able to use unsubscribe --all.

Comment 2 Devan Goodwin 2012-06-05 12:56:18 UTC
There is a separate bug for reporting there are no subscriptions to remove if none are present, which should help this situation as well.


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