Description of problem: When using the RHCI ISO to install RHEL7 and RHCI products on a system, no pem files are populated in /etc/pki/product. As a result, subscription manager does not recognize products are installed and customers are unable to install RH repos. Version-Release number of selected component (if applicable): RHCI_Sat6_1_Beta_1_compose_20150210.0 How reproducible: Always Steps to Reproduce: 1. Use the RHCI ISO to install RHCI products 2. Run `subscription-manager list` 3. View results Actual results: subscription manager returns `no products installed` Expected results: subscription manager correctly returns a list of products that RHCI installs Additional info: thomasmckay has provided a link below to pem files that may be used to populate the /etc/pki/product directory. [1] https://mojo.redhat.com/docs/DOC-103535
Plan to learn how rel-eng addresses this for RHEL ISOs and follow same process.
QE please re-test
"subscription manager list" is run on Sat 6 (RHCI) server where RHCI is installed. It can be run anytime after Anaconda finishes and the system reboots. On tech preview rc-1, still receive "No installed products to list"
Using ISO RHCI-6.0-RHEL-7-20150821.0-RHCI-x86_64-dvd1.iso I now see that subscription-manager list shows "Red Hat Cloud Infrastructure" I was able to run: subscription-manager register subscription-manager attach --auto subscription-manager repos now shows repos are available. Moving to ON_QA to ask for QE to examine if this is sufficient.
Product Name is still "Red Hat Cloud Infrastructure" and Repos Names contain the same string. Testing using: subscription-manager repos --enable=rhci-6-for-rhel-7-preview-rpms --enable=rhcs-6-for-rhel-7-rpms"
This issue is still present in ISO of 826.1
Let's recheck with 8/28.2. rel-eng has updated the certs
works with tech preview rc-4
TP2 RC8 has regression: subscription-manager list No installed products to list
TP2 RC9 has the fix
Verified on QCI-1.2-RHEL-7-20160621.t.0.
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-2016:1862