Bug 1369579

Summary: fusor-installer doesn't check if system already registered
Product: Red Hat Quickstart Cloud Installer Reporter: Thom Carlin <tcarlin>
Component: fusor-installerAssignee: Derek Whatley <dwhatley>
Status: CLOSED ERRATA QA Contact: bmorriso
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0CC: bmorriso, dwhatley, jesusr, tsanders
Target Milestone: gaKeywords: Triaged
Target Release: 1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-09-13 16:37:18 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:

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