client is registered but no licenses consumed

Latest response

I testing out a new Red Hat Satellite Server for the first time. I was able to connect the local system with subscription-manager but "yum install katello-agent' fails with a PYCURL ERROR 22 - "The requested URL returned error: 404 NOT FOUND" error.

Although the client shows that it is registered, when I look at the Content -> Subscriptions -> Red Hat Enterprise Linux Server, Standard (Physical or Virtual Nodes) page the Servers shows 0 Licenses Consumed.

The Server sits on a DMZ while the client is on the Trusted network. The ports opened between the two are 22, 80, and 443.

I have no idea what I am missing and any help would be appreciated.

LV
Log in to join the conversation

Responses

LV Newbie 15 points
14 May 2018 3:09 PM

Followup:

Rebooted the Satellite Server and everything showed up but I have a new problem. When doing a yum update the repolist is successfully downloaded and the list of updates is successfully displayed on the client. When asked if "Is this ok [y/N]: I accept the updates but then get the dreaded "[Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found".

Looking at the foreman-ssl_access_ssl.log I see "GET /streamer/var/lib/pulp/content/units/rpm/81/.../... but the rpm sub-directory under the content directory does not exist on the Satellite server.

Is there a switch I forgot or mis-set during the satellite-installer --scenario satellite command. For what it's worth, we are setting this Sat Server up as simply as possible, no dhcp, no dns as that is all supplied by the Active Directory infrastructure.

ir. Jan Gerrit Kootstra's picture Guru 6222 points
14 May 2018 4:19 PM

Hi Leland,

Did you run repository sync's already? Without sync plans in place or doing manual repository syncs, the repos are empty and the directory tree is not created on disc.

Regards,

Jan Gerrit

LV Newbie 15 points
15 May 2018 3:02 PM

Jan,

Thanks for the reply.

Yes, I did. Here is what I found.

When I first set up the repositories I chose only the Red Hat 7.5 workstations and Red Hat 6.9 Server repos (the first tests involved Red Hat 6.9 servers only). The Red Hat 6.9 yum updates consistently failed, unable to find the repodata files. I then set the repositories for the entire Red Hat 6 Server series and synced the repos. Everything started working correctly after that, the yum command from the servers finding the repodata and packages within the 6.9 Server repo group.

From now on I will sync the entire repos for all our distros.

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.