Bug 1334723

Summary:	[RFE] Cannot resubscribe a system
Product:	Red Hat Enterprise Linux 7	Reporter:	wanghui <huiwa>
Component:	cockpit	Assignee:	Dominik Perpeet <dperpeet>
Status:	CLOSED ERRATA	QA Contact:	qe-baseos-daemons
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.2	CC:	bugs, cshao, fdeutsch, huzhao, jscotka, leiwang, weiwang, yaniwang
Target Milestone:	pre-dev-freeze	Keywords:	Extras, FutureFeature
Target Release:	7.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-12-06 17:43:31 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:	1329957

Description wanghui 2016-05-10 12:16:54 UTC

Description of problem:
It should be better to provide a way to subscribe again. If the subscribe server changes, customer will need to subscribe again. But I can not find the way to re-subscribe this time.

Version-Release number of selected component (if applicable):
rhev-hypervisor7-ng-20160506.0.el7
imgbased-0.6-0.1.el7ev.noarch
cockpit-ovirt-0.5.1-0.0.ovirt40.el7ev.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Install rhev-hypervisor7-ng-3.6-20160506.0.el7
2. Suscribe to RHSM with username and password.
3. Check the subscribe status.

Actual results:
1. It is subscribed succeed. But there is no clear way to re-subscribe.

Expected results:
1. It should provide a way to subscribe again.

Additional info:

Comment 1 Stef Walter 2016-05-25 06:50:26 UTC

I've updated the title to reflect the bug report.

Comment 3 Dominik Perpeet 2016-11-10 09:57:27 UTC

System can be unregistered and then registered again, fixed upstream in Cockpit 119

Comment 7 errata-xmlrpc 2016-12-06 17:43:31 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2888.html