Bug 1334723 - [RFE] Cannot resubscribe a system
Summary: [RFE] Cannot resubscribe a system
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: cockpit
Version: 7.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: pre-dev-freeze
: 7.3
Assignee: Dominik Perpeet
QA Contact: qe-baseos-daemons
Depends On:
Blocks: ovirt-node-ng-platform
TreeView+ depends on / blocked
Reported: 2016-05-10 12:16 UTC by wanghui
Modified: 2016-12-06 17:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2016-12-06 17:43:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2888 0 normal SHIPPED_LIVE cockpit bug fix and enhancement update 2016-12-06 22:41:11 UTC

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):

How reproducible:

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.


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