No redhat.repo file after subscription

Support
1

Problem:
No redhat.repo created after subscription

Expected outcome:
Redhat.repo file generated

Foreman and Proxy versions:
foreman-tasks 4.1.1
foreman_remote_execution 4.5.0
katello 4.1.0.rc2.1

Foreman and Proxy plugin versions:

Distribution and version:
CentOS Linux release 8.4.2105

Other relevant data:
Hi,

We have different Content Views: Centos 7, Centos 8, PostgreSQL, MAriaDB, etc, with their respective repositories. Now we want to make a Composite View with three of these Content Views. We associate this Composite View an Activation Key. Then when we subscribe a host with this activation key it doesn´t generated any redhat, repo file in the host. We are obviously doing something wrong, but we search in documentation and we don’t find where is the mistake. Can Someone help us?

Thank you,
I

1 Like
2

I ended up here because I just had this same issue, and with a katello install that’s been running great forever.

The system subscription appears to work, everything inside of katello looks perfect, yet, no “redhat.repo” file gets created on the host I am registering.

I eventually ended up looking at /var/log/rhsm/rhsm/log and saw THIS:

2022-11-08 10:31:42,817 [WARNING] subscription-manager:14323:MainThread @connection.py:814 - Clock skew detected, please check your system time
2022-11-08 10:31:42,848 [WARNING] subscription-manager:14323:MainThread @connection.py:814 - Clock skew detected, please check your system time
2022-11-08 10:33:15,853 [WARNING] subscription-manager:14330:MainThread @connection.py:814 - Clock skew detected, please check your system time
2022-11-08 10:33:15,932 [WARNING] subscription-manager:14330:MainThread @connection.py:814 - Clock skew detected, please check your system time

So… the issue is, if the time of the clock of the server being registered varies too much from the katello host, bam. You have this issue.

This was a NEW host, and I did not notice the clock was 6 hours off.

I reset the system time, and VOILA: the system registered properly AND redhat.repo properly created.

(Rocky Linux 8 was the OS of the client if anyone cares)