Description of problem:{}

Registering host to the capsule with synced RH content creates a different (incorrect) baseurl in repo config on client compared to host registered to satellite directly.

This leads to 404 on client when trying to install content.

Excerpt from /etc/yum.repos.d/redhat.repo on client when registered to Capsule:

[rhel-8-for-x86_64-appstream-rpms]
name = Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs)
baseurl = https://<capsule_hostname>/pulp/content/AjcmCW/HqrODs/afyanmVOCU/content/dist/rhel8/$releasever/x86_64/appstream/os 

The same for host registered to Satellite:

[rhel-8-for-x86_64-appstream-rpms]
name = Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs)
baseurl = https://<satellite_hostname>/pulp/content/wQeDdoBmL/bFOmLvMplt/RyRpvK/content/dist/rhel8/8.10/x86_64/appstream/os

Note that the Capsule version uses $releasever in the baseurl path, which translates to 8 in this case instead of 8.10 which leads to incorrect path

How reproducible:

Always

Is this issue a regression from an earlier version:

most likely yes

Steps to Reproduce:

1. sync red hat content to satellite and then to the capsule, create activation key

2. register host to the capsule

3. try to install content on client

Actual behavior:
as described above

Expected behavior:
correct baseurl created

Business Impact / Additional info:

I can share/recreate the setup using automation if requested