Bug 1369579 - fusor-installer doesn't check if system already registered
Summary: fusor-installer doesn't check if system already registered
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Quickstart Cloud Installer
Classification: Red Hat
Component: fusor-installer
Version: 1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ga
: 1.0
Assignee: Derek Whatley
QA Contact: bmorriso
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-23 20:33 UTC by Thom Carlin
Modified: 2016-09-13 16:37 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-09-13 16:37:18 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2016:1862 0 normal SHIPPED_LIVE Red Hat Quickstart Installer 1.0 2016-09-13 20:18:48 UTC

Description Thom Carlin 2016-08-23 20:33:19 UTC 
Description of problem:

fusor-installer always starts with "Register Hosts For Updates" = false

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

QCI-1.0-RHEL-7-20160819.t.0

How reproducible:

100%

Steps to Reproduce:
1. Install RHEL 7
2. Register system
3. launch-fusor-installer
4. Examine 15

Actual results:

15. Register Host For Updates | false

Expected results:

15. Register Host For Updates | true

Additional info:

Need to check if system is already registered
Comment 3 Derek Whatley 2016-08-29 18:28:51 UTC 
PR at https://github.com/fusor/fusor-installer/pull/91
Comment 4 bmorriso 2016-08-31 16:46:19 UTC 
Verified on compose QCI-1.0-RHEL-7-20160831.t.0

On a system where I had already registered with subscription-manager, I attempted to register via the fusor-installer and received this message:

"System is already registered to the customer portal. Re-register? [Y/n]"

I was able to re-register successfully this way.
Comment 6 errata-xmlrpc 2016-09-13 16:37:18 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://access.redhat.com/errata/RHEA-2016:1862
Note You need to log in before you can comment on or make changes to this bug.