Red Hat Bugzilla – Bug 884657
the server-6-ost-folsom channels need to be mapped into channel-cert-mapping.txt
Last modified: 2013-11-21 16:22:56 EST
Description of problem:
CDN Product Baseline RHN Channel 'rhel-x86_64-server-6-ost-folsom' is accounted for in the subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-6/channel-cert-mapping.txt'. expected:<true> but was:<false>
CDN Product Baseline RHN Channel 'rhel-x86_64-server-6-ost-folsom-debuginfo' is accounted for in the subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-6/channel-cert-mapping.txt'. expected:<true> but was:<false>
Version-Release number of selected component (if applicable):
[root@jsefler-6server ~]# rpm -q subscription-manager-migration-data
Steps to Reproduce:
[root@jsefler-6server ~]# grep ost-folsom /usr/share/rhsm/product/RHEL-6/channel-cert-mapping.txt
There's a slight problem here. The ID 191 maps to two different certificates.
% find -name '*191*.pem'
Consequently, the script that generates the channel-cert-mapping file doesn't know which certificate to map to.
Although both of the product ids are the same (191), they appear to be different versions of the same product....
[root@jsefler-6 rhnDefinitionsDir]# rct cat-cert product_ids/openstack/Server-OpenStack-x86_64-0b9893c79701-191.pem | grep Product: -A6
Name: Red Hat OpenStack
[root@jsefler-6 rhnDefinitionsDir]# rct cat-cert product_ids/openstack/Server-OpenStack-x86_64-b83069ace8bd-191.pem | grep Product: -A6
Name: Red Hat OpenStack
Clearly, the RHN *folsum* channels correspond to Server-OpenStack-x86_64-0b9893c79701-191.pem, but that's not so programatically obvious from parsing the product-baseline.json.
I'm not sure info to provide other than "products will have multiple versions". There will be multiple certificates for RHEV: 3.0 and 3.1 later today and JBoss EWS (1.x and 2.x) later this week.
Note that each version of OpenStack will make to a different set of RHN channels.
rhel-x86_64-server-6-ost-preview -> Essex
rhel-x86_64-server-6-ost-folsom -> Folsom
So, we should be able to handle that mapping in the migration tool. However, we may need to move the certs around so that the tool knows which cert to use for each channel. Alex, what do you think?
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
The ost folsom channels are in the latest product-certs.json.
$ grep ost product-certs.json
[root@jsefler-6 ~]# rpm -q subscription-manager-migration-data
[root@jsefler-6 ~]# grep ost /usr/share/rhsm/product/RHEL-6/channel-cert-mapping.txt
VERIFIED: The folsom and preview mappings are now included in subscription-manager-migration-data, but it now looks like we need mappings for ost-3 too. That'll get opened as a new bug.
Regarding the mapping of multiple channels to a product cert that shares a common product ID (e.g 191). This will be handled by bug 1006985
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.