Bug 755834 - Unable to unsubscribe in firstboot
Summary: Unable to unsubscribe in firstboot
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: beta
: 6.4
Assignee: Bryan Kearney
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 771481
TreeView+ depends on / blocked
 
Reported: 2011-11-22 07:14 UTC by Marian Ganisin
Modified: 2012-08-13 20:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-13 20:42:25 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Marian Ganisin 2011-11-22 07:14:12 UTC
Description of problem:
I subribed machine during firstboot. In same time I decided I would like to unsubscribe. Still in firstboot I selected my subscription and presed Unsubscribe.
Operation failed with message: Insufficient permissions.

Version-Release number of selected component (if applicable):
subscription-manager-firstboot-0.98.3-1.el5
subscription-manager-gnome-0.98.3-1.el5
subscription-manager-0.98.3-1.el5
firstboot-1.4.27.9-1.el5

Steps to Reproduce:
1. Subscribe in firstboot,
2. select subscription,
3. press Unsubscribe button.

Comment 3 RHEL Program Management 2012-07-10 06:58:13 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2012-07-11 02:08:26 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 5 Bryan Kearney 2012-08-13 20:42:25 UTC
Given the new workflow, this will not be feasible. Users will need to use subscription-manager tool after registration.


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