With a previous version of Foreman, I was only able to access one repository per product.
It was then suggested that I upgrade due to the number of updates to pulp, Foreman, etc. So, I built a new host with a fresh install of Foreman+Katello (no data was migrated); I configured Foreman as I had previously with success until my aforementioned encounter with 1.24. I subscribed my CentOS 8 Content Host and discovered all repos but one are available.
I have seven repositories, three of which are CentOS 8:
- PowerTools
- AppStream
- BaseOS
When I run subscription-manager repos --list , only the BaseOS repo is missing. I have validated the repo is syncing, has content, is published in the Content View, and that the Content Host has access to said repo. In checking the repository configurations, I noticed they all have â Architecture: Default â.
However, when analyzing the JSON returned by wget --certificate=/etc/pki/consumer/cert.pem --private-key=/etc/pki/consumer/key.pem https://foreman.mydomain.com/rhsm/consumers/d2579e09-f65c-4c26-9573-a41b665bc599 , I noticed that the BaseOS repo has arches : x86_64 in the array. The six repos that are showing as available via subscription-manager have arches : null in their arrays.
I have tried to set and reset the Architecture setting for the repos, but it doesnât appear to have any effect and the issue remains that BaseOS is unavailable. I also noticed the entitlement certificate that subscription-manager receives doesnât appear to have the BaseOS repo listed.
It would appear something is not right in how data is being provided to subscription-manager .
# rct cat-cert /etc/pki/entitlement/3288316626973312046.pem
+-------------------------------------------+
Entitlement Certificate
+-------------------------------------------+
Certificate:
Path: /etc/pki/entitlement/3288316626973312046.pem
Version: 3.4
Serial: 3288316626973312046
Start Date: 2020-10-21 14:54:49+00:00
End Date: 2049-12-01 00:00:00+00:00
Pool ID: 8a9084ac754b9a7a01754ba7cceb0003
Subject:
CN: 2d28efe990c4448094f80eeca504fa84
O: My_Awesome_Org
Issuer:
C: US
CN: foreman-client.mydomain.com
L: My City
O: My Awesome Org
OU: Infrastructure
ST: My State
Product:
ID: 927803325001
Name: CentOS
Version:
Arch: ALL
Tags:
Brand Type:
Brand Name:
Order:
Name: CentOS
Number:
SKU: 927803325001
Contract:
Account:
Service Type:
Roles:
Service Level:
Usage:
Add-ons:
Quantity: Unlimited
Quantity Used: 1
Socket Limit:
RAM Limit:
Core Limit:
Virt Only: False
Stacking ID:
Warning Period: 0
Provides Management: False
Authorized Content URLs:
/My_Awesome_Org/CentOS_8_Virtual_Servers/CentOS_8_Virtual_Servers/custom/CentOS/8_-_AppStream
/My_Awesome_Org/CentOS_8_Virtual_Servers/CentOS_8_Virtual_Servers/custom/CentOS/8_-_PowerTools
Content:
Type: yum
Name: 8 - AppStream
Label: My_Awesome_Org_CentOS_8_-_AppStream
Vendor: Custom
URL: /My_Awesome_Org/CentOS_8_Virtual_Servers/CentOS_8_Virtual_Servers/custom/CentOS/8_-_AppStream
GPG: ../../katello/api/v2/repositories/3/gpg_key_content
Enabled: True
Expires: 1
Required Tags:
Arches: ALL
Content:
Type: yum
Name: 8 - PowerTools
Label: My_Awesome_Org_CentOS_8_-_PowerTools
Vendor: Custom
URL: /My_Awesome_Org/CentOS_8_Virtual_Servers/CentOS_8_Virtual_Servers/custom/CentOS/8_-_PowerTools
GPG: ../../katello/api/v2/repositories/5/gpg_key_content
Enabled: True
Expires: 1
Required Tags:
Arches: ALL
Again, Iâve verified the Activation Key, Lifecycle Environment, and Content View are all properly configured (and published). Iâve verified the Content Host shows in Foreman as having access to the BaseOS repo. However, subscription-manager and the data it receives from the /rhsm endpoint on the Foreman host are reporting different.
Currently, this only appears to affect CentOS 8. I have not tested any of my CentOS 7, RHEL 7, or RHEL 8 hosts yet.
Most gracious thanks in advance for any help that can be provided.
