Created attachment 1263177 [details] log files Description of problem: Cannot enable "rhel-7-server-rhvh-4*" repo since /etc/pki/product-default/328.pem has wrong tag: rhvh,rhvh-4-1 Version-Release number of selected component (if applicable): redhat-virtualization-host-4.1-0.20170309.0 subscription-manager-1.17.15-1.el7.x86_64 yum-3.4.3-150.el7.noarch How reproducible: 100% Steps to Reproduce: 1. Install RHVH 4.1 2. Subscription manager register and attach to cdn rhvh channel 3. yum search dropwatch/systemtap/vim-enhanced 4. subscription-manager repos --list-enabled 5. subscription-manager repos --enable=rhel-7-server-rhvh-4* 6. Check the /etc/pki/product-default/328.pem Actual results: After step 3, yum search fail, no matches found After step 4, [root@dhcp-10-157 ~]# subscription-manager repos --list-enabled There were no available repositories matching the specified criteria. After step 5, [root@dhcp-10-157 ~]# subscription-manager repos --enable=rhel-7-server-rhvh-4* Error: 'rhel-7-server-rhvh-4*' does not match a valid repository ID. Use "subscription-manager repos --list" to see valid repositories. After step 6, product tag is rhvh,rhvh-4-1 Expected results: After step 3, yum search successfully After step 4, rhel-7-server-rhvh-4* repos should be listed After step 5, rhel-7-server-rhvh-4* repos should be enabled successfully. After step 6, product tag should be rhvh,rhvh-4 Additional info:
Created attachment 1263178 [details] pem
For checking the tag in certification, we use the CLI rct # rct cc xxx.pem then you can get the tag info
The bug doesn't occur with redhat-virtualization-host-4.1-20170202.0, so add "Regression" keyword.
(In reply to Wei Wang from comment #3) > The bug doesn't occur with redhat-virtualization-host-4.1-20170202.0, so add > "Regression" keyword. the certificate was updated in 4.1 after bug 1419483 was reported
Joey, can this be fixed from the channels, or do we need another cert?
According to comment #10, change status to VERIFIED.
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. https://access.redhat.com/errata/RHEA-2017:1114