Bug 2054971

Summary:	Enable registration by default
Product:	Red Hat Satellite	Reporter:	Nagoor Shaik <nshaik>
Component:	Installation	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED ERRATA	QA Contact:	Omkar Khatavkar <okhatavk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.11.0	CC:	egolov, ehelms, ekohlvan, gtalreja, mdolezel
Target Milestone:	6.11.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-07-05 14:33:19 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:

Description Nagoor Shaik 2022-02-16 06:25:38 UTC

Describe the issue: 

On a fresh/upgraded Satellite 7.0, registration feature is disabled by default due to 

[1] - https://projects.theforeman.org/issues/33864/
[2] - https://github.com/theforeman/foreman-installer/pull/731#issue-1047738473

As an end user, if I would like to register my hosts using the Global registration template, the Capsule doesn't allow it.

Steps to check:

1. Install/Upgrade just a Satellite 7 server 
2. Navigate to Hosts > Register Host 
3. Check the Capsule field, which is greyed out saying "Nothing to Select"

This is due to both Registration and Templates features are both disabled by default on the default Capsule aka. Satellite.

We need to document the steps to enable if one wishes to enable them to use Global registration feature with just the Satellite 

Running below command will enable both the Registration and Templates feature on the Satellite server

 # satellite-installer --foreman-proxy-registration true --foreman-proxy-templates true

Comment 7 Ewoud Kohl van Wijngaarden 2022-02-24 13:27:47 UTC

Looking at this I think some additional work is needed.

First of all some background. In upstream we disabled the feature by default since the templates feature (on which it depends) is not enabled.

However, in the downstream Capsule scenario the templates feature is enabled by default. That means we could enable registration by default. That means the instructions for users would be easier, essentially it should work out of the box.

Just to be clear, we don't enable this on the Satellite scenario since AFAIK there is no benefit. However, I may be missing something and in that case, I'd be open to doing so.

How do we approach this process wise? Open a new BZ to track enabling by default?

Comment 8 Ewoud Kohl van Wijngaarden 2022-03-02 13:50:26 UTC

Changing this to an installer bug. I think it should be merged before 7.0.0.

Comment 9 Nagoor Shaik 2022-03-03 06:15:47 UTC

Hello Ewoud,

I will try to answer this part

Just to be clear, we don't enable this on the Satellite scenario since AFAIK there is no benefit. However, I may be missing something and in that case, I'd be open to doing so.
>>> This is particularly for customers who has *single* Satellite deployed for managing content hosts. I believe there is no harm or unintended side-effects if we enabled by default on Satellite.

Comment 10 Ewoud Kohl van Wijngaarden 2022-03-03 12:53:03 UTC

AFAIK you can use the registration feature directly on Foreman and you don't need it on the Smart Proxy. It would only a layer of indirection. However, I haven't checked this recently.

And the harm would be that you do get the templates feature enabled, which means you can have added confusion. Suddenly you may need to select a templates proxy where there is only one option. It would require enabling HTTP and opening port 8000 on the Satellite server. Those are much bigger changes.

Comment 14 Omkar Khatavkar 2022-04-18 05:34:31 UTC

Verified this with satellite capsule Satellite 7.0 and Snap 16. Both are getting enabled after adding a smart proxy.   

[root@ ~]# satellite-installer --full-help | grep -E '\-\-foreman.*proxy.*registration |\-\-foreman.*proxy\-templates '
    --foreman-proxy-registration  Enable Registration feature (current: true)
    --foreman-proxy-templates     Enable templates feature (current: true) 

@ekohlvan I still see that the registration feature is not enabled by default from the installer settings which differs from the statement you added on https://bugzilla.redhat.com/show_bug.cgi?id=2054971#c10  

[root@ ~]# rpm -qa | grep satellite-7
satellite-7.0.0-0.7.beta.el7sat.noarch
[root@ ~]# satellite-installer --full-help | grep -E '\-\-foreman.*proxy.*registration |\-\-foreman.*proxy\-templates '
    --foreman-proxy-registration  Enable Registration feature (current: false)
    --foreman-proxy-templates     Enable templates feature (current: false)

My understanding was that if the registration feature is default enabled why it is not true? (It could be raised different bug for this)

Comment 21 errata-xmlrpc 2022-07-05 14:33:19 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 (Moderate: Satellite 6.11 Release), 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/RHSA-2022:5498

Comment 22 Red Hat Bugzilla 2023-09-18 04:32:06 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days