Add RHEL Repos into Foreman

I have added my manifest to Foreman and enabled the virt-who configuration via the cli. When I click on Content->Red Hat Repositories and any repro I get the following error. “No repositories available.”

Foreman and Proxy versions:2.3.3
Foreman and Proxy plugin versions:2.3.3
Distribution and version:

I feel like I missed a step some but not sure where. When I looked that the virt-who configuration I did not find anywhere to add my rhel creds to get downloads enabled.

[root@tjossforeman01 a05mja1]# tail -0f /var/log/foreman/production.log | grep -i RHEL
2021-05-07T13:52:49 [I|app|fcbda670] Started GET “/katello/api/v2/repository_sets?organization_id=3&with_active_subscription=true&search=(((name+!~+source+rpm)+and+(name+!~+debug+rpm)+and+(content_type+%3D+yum)+and+(label+!~+beta)+and+(label+!~+htb)+and+(name+!~+beta)+and+(product_name+!~+beta)))+and+(label+%3D+rhel-8-for-x86_64-baseos-rpms+or+label+%3D+rhel-8-for-x86_64-baseos-kickstart+or+label+%3D+rhel-8-for-x86_64-appstream-rpms+or+label+%3D+rhel-8-for-x86_64-appstream-kickstart+or+label+%3D+rhel-7-server-rpms+or+label+%3D+rhel-7-server-optional-rpms+or+label+%3D+rhel-7-server-extras-rpms+or+label+%3D+rhel-7-server-eus-rpms+or+label+%3D+rhel-7-server-kickstart+or+label+%3D+rhel-6-server-rpms+or+label+%3D+rhel-6-server-kickstart+or+label+%3D+rhel-5-server-els-rpms+or+label+%3D+satellite-tools-6.8-for-rhel-8-x86_64-rpms+or+label+%3D+rhel-7-server-satellite-tools-6.8-rpms+or+label+%3D+rhel-6-server-satellite-tools-6.8-rpms+or+label+%3D+rhel-5-server-els-satellite-tools-6.8-rpms+or+label+%3D+rhel-7-server-satellite-maintenance-6-rpms+or+label+%3D+rhel-server-rhscl-7-rpms+or+label+%3D+rhel-7-server-satellite-capsule-6.8-rpms+or+label+%3D+rhel-7-server-ansible-2.9-rpms)” for 127.0.0.1 at 2021-05-07 13:52:49 -0400
2021-05-07T13:52:49 [I|app|fcbda670] Parameters: {“organization_id”=>“3”, “with_active_subscription”=>“true”, “search”=>"(((name !~ source rpm) and (name !~ debug rpm) and (content_type = yum) and (label !~ beta) and (label !~ htb) and (name !~ beta) and (product_name !~ beta))) and (label = rhel-8-for-x86_64-baseos-rpms or label = rhel-8-for-x86_64-baseos-kickstart or label = rhel-8-for-x86_64-appstream-rpms or label = rhel-8-for-x86_64-appstream-kickstart or label = rhel-7-server-rpms or label = rhel-7-server-optional-rpms or label = rhel-7-server-extras-rpms or label = rhel-7-server-eus-rpms or label = rhel-7-server-kickstart or label = rhel-6-server-rpms or label = rhel-6-server-kickstart or label = rhel-5-server-els-rpms or label = satellite-tools-6.8-for-rhel-8-x86_64-rpms or label = rhel-7-server-satellite-tools-6.8-rpms or label = rhel-6-server-satellite-tools-6.8-rpms or label = rhel-5-server-els-satellite-tools-6.8-rpms or label = rhel-7-server-satellite-maintenance-6-rpms or label = rhel-server-rhscl-7-rpms or label = rhel-7-server-satellite-capsule-6.8-rpms or label = rhel-7-server-ansible-2.9-rpms)", “api_version”=>“v2”}

I saw similar behavior on RH repositories page recently, refreshing a manifest helped in my case. Not sure about the real cause. @katello may be able to help or ask for more questions to diagnose.

3 Likes

refreshing the RHEL manifest resolved this problem.

3 Likes