Bug 2224170

Summary:	Registering client host with Satellite using Global Registration Template shows "Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d"."
Product:	Red Hat Satellite	Reporter:	Jayant Bhatia <jbhatia>
Component:	Registration	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	NEW ---	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.14.0	CC:	ahumbe, lstejska, nalfassi, rlavi
Target Milestone:	Unspecified	Keywords:	Triaged, UserExperience
Target Release:	Unused
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:		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 Jayant Bhatia 2023-07-20 05:42:00 UTC

Description of problem:

While registering client host with Satellite using Global registration Template, the registration is successful but below message is shown in the logs which leads to confusion for users.
~~~
This system is not registered with an entitlement server. You can use subscription-manager to register.

Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".
~~~


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


How reproducible: Always


Steps to Reproduce:
1. Navigate to Satellite WebUI -> Hosts -> Register Host and generate the curl command after filing all fields.
2. Take any RHEL machine which is either registered to a Satellite or registration was attempted on that RHEL machine before.
3. Run the curl command to register the client host with Satellite.


Actual results: Below message is seen in screen during the registration process which is confusing .

~~~
This system is not registered with an entitlement server. You can use subscription-manager to register.

Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".
~~~


Expected results: The above errors should not be generated during registration process

Comment 4 Leos Stejskal 2023-07-25 11:40:54 UTC

Hi,
this does not look like a bug in the registration, but rather a subscription.

See the error:
```
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered with an entitlement server. You can use subscription-manager to register.

Error: There are no enabled repositories in "/etc/yum.repos.d", "/etc/yum/repos.d", "/etc/distro.repos.d".
The system has been registered with ID: 5bb5cedf-133c-42fe-b45a-7656c346da23
The registered system name is: dhcp131-83.gsslab.pnq2.redhat.com
```

What repositories do you have enabled for the OS?

Comment 5 Jayant Bhatia 2023-07-26 02:16:47 UTC

The registration is always successful but observed error is misleading. I tried with RHEL-9 BaseOS and Appstream repo. The same error is observed irrespective of the repo being made available to the registered client host.

Comment 6 Leos Stejskal 2023-08-02 08:17:14 UTC

> The registration is always successful but the observed error is misleading.

The error is coming from the yum, or subscription-manager, not sure right now,
there isn't much we can do with it.

> The same error is observed irrespective of the repo being made available to the registered client host.

Can you share steps on how to reproduce the issue? This would mean that registration doesn't work
but we didn't get any issues from QAs nor from the customers, so I guess there are maybe some steps missing in the setup

Comment 7 Marek Hulan 2023-08-02 12:11:04 UTC

We could potentially silence the subscription-manager commands we run before the actual registration

https://github.com/theforeman/foreman/blob/90a5e4c341051915c8f915e7259f4b9673a25a2c/app/views/unattended/provisioning_templates/registration/global_registration.erb#L187

We already redirect stdout to /dev/null later

https://github.com/theforeman/foreman/blob/90a5e4c341051915c8f915e7259f4b9673a25a2c/app/views/unattended/provisioning_templates/registration/global_registration.erb#L198-L199

We could potentially also silence the STDERR, but at the same time, this may be needed while debugging.