Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1519975

Summary: rhel-x86_64-server-7-cf-me-4.* channel maps are absent from channel-cert-mapping.txt
Product: Red Hat Enterprise Linux 7 Reporter: John Sefler <jsefler>
Component: subscription-manager-migration-dataAssignee: candlepin-bugs
Status: CLOSED WONTFIX QA Contact: Red Hat subscription-manager QE Team <rhsm-qe>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.5CC: ahills, csnyder, khowell, redakkan
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-09 13:53:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Sefler 2017-12-01 20:22:44 UTC
Description of problem:


RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.0' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>

RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.1' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>

RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.2' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>

RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.5' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>


RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.0-debuginfo' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>

RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.1-debuginfo' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>

RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.2-debuginfo' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>

RHN Classic channel 'rhel-x86_64-server-7-cf-me-4.5-debuginfo' is accounted for in subscription-manager-migration-data file '/usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt'. expected:<true> but was:<false>


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
[root@jsefler-rhel7 ~]# grep "rhel-x86_64-server-7-cf-me-4" /usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt
[root@jsefler-rhel7 ~]# 

Actual results:
above - no hits

Expected results:
 expected to find product cert mappings for channels:
   rhel-x86_64-server-7-cf-me-4.0
   rhel-x86_64-server-7-cf-me-4.1
   rhel-x86_64-server-7-cf-me-4.2
   rhel-x86_64-server-7-cf-me-4.5
   rhel-x86_64-server-7-cf-me-4.0-debuginfo
   rhel-x86_64-server-7-cf-me-4.1-debuginfo
   rhel-x86_64-server-7-cf-me-4.2-debuginfo
   rhel-x86_64-server-7-cf-me-4.5-debuginfo


Additional info:
  Before subscription-manager-migration-data can be fixed, an update to upstream http://git.app.eng.bos.redhat.com/git/rcm/rcm-metadata.git/tree/cdn/product-certs.json is required.

Comment 2 John Sefler 2017-12-01 20:30:40 UTC
Version-Release number of selected component (if applicable):

[root@jsefler-rhel7 ~]# rpm -q subscription-manager-migration-data
subscription-manager-migration-data-2.0.37-1.el7.noarch

Comment 3 Chris Snyder 2017-12-04 15:48:42 UTC
Please see comment 0 about product-certs.json.


Lubos,

Are you the right resource to work with on getting this file updated?

Thanks,
Chris

Comment 4 John Sefler 2020-05-15 02:21:18 UTC
[root@ibm-x3650m4-01-vm-06 ~]# rpm -q subscription-manager-migration-data
subscription-manager-migration-data-2.0.55-1.el7.noarch
[root@ibm-x3650m4-01-vm-06 ~]# 
[root@ibm-x3650m4-01-vm-06 ~]# grep "rhel-x86_64-server-7-cf-me-4" /usr/share/rhsm/product/RHEL-7/channel-cert-mapping.txt
[root@ibm-x3650m4-01-vm-06 ~]# 

This is still a valid bug, but likely a low severity bug.

Comment 5 Rehana 2020-05-19 09:47:51 UTC
Thanks John , reported a RCM ticket to track this. 

Note : Adding triage keyword

Comment 7 Rehana 2020-06-09 13:53:47 UTC
Based on the comment on jira , moving the bug to close wont fix .