Looking at Channel and Certificate Mappings

The subscription-manager-migration-data package contains a mapping file that maps RHN Classic channels to Certificate-based CentOS Network product certificates. This file (/usr/share/rhsm/product/RHEL-5/channel-cert-mapping.txt) uses simple keys to map the values:

channel_name: product_name-hash-product_cert.pem

For example, this maps the Community Enterprise Linux Client channel to the corresponding product certificate:

rhel-i386-client-workstation-5: Client-Workstation-i386-b0d4c042-6e31-45a9-bd94-ff0b82e43b1a-71.pem

During migration, that mapping is translated into product_cert.pem and the product certificate is copied into the /etc/pki/product directory. For the rhel-i386-client-workstation-5, this migrates to the 71.pem product certificate (the last two digits of the mapping).

However, many channels are available for legacy systems only or have not yet released an X.509 product certificate. In that case, the channel has no mapping.

jbappplatform-4.3.0-fp-i386-server-5-rpm: none

This can create a situation where not all channels are migrated over to Certificate-based CentOS Network or where products are not fully subscribed.