Bug 1374997

Summary:	[RFE] [Installation Guide] Enhance 'Before You Begin' in 'Registering Capsule Server to Satellite Server'
Product:	Red Hat Satellite	Reporter:	Reartes Guillermo <greartes>
Component:	Docs Install Guide	Assignee:	Lucie Jirakova <ljirakov>
Status:	CLOSED NEXTRELEASE	QA Contact:	Stephen Wadeley <swadeley>
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2.0	CC:	adahms, greartes, sbream, swadeley
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-07-20 12:34:39 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 Reartes Guillermo 2016-09-11 15:20:44 UTC

Document URL:

https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/installation-guide#registering_capsule_to_satellite

Section Number and Name:
4.1. Registering Capsule Server to Satellite Server ------> Before You Begin

Describe the issue:

The guide gives instructions before attemting to start the Sat6.2 Capsule install. I propose a small ehnancement to the "Before You Begin".

SETP #1:
The system is already registered to RHCP directly and is using PROXY (in rhsm.conf)

STEP #2:
# curl -kO https://sixthsat2.example.com/pub/katello-ca-consumer-latest.noarch.rpm

STEP #3:
# rpm -ivh katello-ca-consumer-latest.noarch.rpm

STEP #4:
Try to register to Sat6.2 ...

# subscription-manager register --org "DemoCorp"
This will fail, it will say "already registered" (and that's true)

# subscription-manager unregister
This will fail, beacuse the proxy settings are still in place (!)

# subscription-manager clean
This will work (but the system will still exists on RHCP, and must be manually deleted later)

# subscription-manager register --org "DemoCorp"
Registrándose a: sixthsat2.example.com:443/rhsm
Nombre de usuario: admin
Contraseña:
Error de red, no puede conectarse al servidor. Por favor, consulte /var/log/rhsm/rhsm.log para obtener más información.

And this will also fail, also because the proxy settings are still in place (!) but they are not needed to access the Sat6.2 instance. The proxy leads to nowhere now...

I recomend to update the section 4.1, specially the section "Before You Begin"

* It should mention that the system must be unregistered from RHCP

* Proxy settings must be manually reviewed (rhsm.conf), maybe they are ok, maybe they are not (most likely)

* In case of RHEL6, the system must alse be unregisterd from RHN Classic (and maybe also removed from Sat5)

In my case i build and prepare the system to be a Sat6.2 capsule outside of the Sat6.2.

It was direclty registered to RHCP via proxy, so it is reasonable that i first unsuscribe it and remove the proxy before starting the Sat6.2 installation.

Cheers.

Comment 1 Andrew Dahms 2016-10-13 01:01:35 UTC

Assigning to Lucie for review.

Comment 2 Lucie Jirakova 2017-06-22 14:08:14 UTC

(In reply to Reartes Guillermo from comment #0)

Hello Reartes,

> Document URL: 
> 
> https://access.redhat.com/documentation/en/red-hat-satellite/6.2/single/
> installation-guide#registering_capsule_to_satellite

Thank you for reporting this bug. Since it was first recorded in Bugzilla, the procedure you refer to has been revised and updated a couple of times, and I believe this issue has been resolved along the way. 

Please have a look at the current description under the URL above, and let us know if you think it's OK now, or if you feel that something is still wrong or missing. Most of what you mention should not be an issue any more.

An enhancement I can think of would be an explicit note advising users who use a proxy to check the rhsm.conf file, if that helps.

Thank you!

Comment 3 Stephen Wadeley 2017-07-12 14:07:49 UTC

Hello

If you install a RHEL server and make no changes then there will be no proxy config, so how about we change this:

Capsule Server has the same requirements for installation as Satellite Server.

this:
Capsule Server has the same requirements for installation as Satellite Server, with the additional requirement that you have not configured it to use a proxy to connect to the Red Hat CDN.

How about add to the "Before You Begin" list:

Revert any changes related to the use of proxies which prevent access to Red Hat Satellite.


In the section "Supported Operating Systems"

Below this:
It is recommended that the Satellite Server be a freshly provisioned system. Using the system for anything other than running Satellite is not supported. 

Add:
It is recommended that Capsule Servers be freshly provisioned systems and not registered to the Red Hat CDN.

Comment 4 Steve Bream 2017-07-12 15:27:13 UTC

Hello,

I like these changes. One small tweak - can we make the statement of requirements for Capsule Server actionable? Change:

Capsule Server has the same requirements for installation as Satellite Server, with the additional requirement that you have not configured it to use a proxy to connect to the Red Hat CDN.

To something similar to:

Capsule Server has the same requirements for installation as Satellite Server. Additionally, you much configure Capsule Server to use a proxy to connect to the Red Hat CDN.

Everything else looks good to me.

Comment 5 Stephen Wadeley 2017-07-13 07:03:02 UTC

(In reply to Steve Bream from comment #4)
> Hello,
> 
> I like these changes. One small tweak - can we make the statement of
> requirements for Capsule Server actionable? Change:
> 
> Capsule Server has the same requirements for installation as Satellite
> Server, with the additional requirement that you have not configured it to
> use a proxy to connect to the Red Hat CDN.
> 
> To something similar to:
> 
> Capsule Server has the same requirements for installation as Satellite
> Server. Additionally, you 
must not have configured
 Capsule Server to use a proxy to
> connect to the Red Hat CDN.
>

Comment 6 Steve Bream 2017-07-13 12:06:52 UTC

Got it, thanks Stephen, I had the process backwards. Now that I get it I prefer your original wording.

Comment 7 Lucie Jirakova 2017-07-17 12:18:39 UTC

Hello Stephen, Steve,

Thank you for your help and suggestions. I will use Stephen's wording as per comment 3.