Description of problem: after subscribing a system the registration snippet uses yum-config-manager to enable the openstack repo. yum-config-manager reports it does but does not actually do it. Version-Release number of selected component (if applicable): How reproducible: every time Steps to Reproduce: 1. use subscription manager with the openstack installer 2. 3. Actual results: puppet fails to run because the repo doesn't get enabled Expected results: repo should get enabled and puppet should run Additional info: work around it to use subscription manager to enable the repo instead of yum-config-manager
submitted a patch upstream https://github.com/theforeman/foreman-installer-staypuft/pull/41
Merged upstream
Verified: rhel-osp-installer-0.1.10-2.el6ost.noarch Environment: openstack-foreman-installer-2.0.21-1.el6ost.noarch ruby193-rubygem-foreman_openstack_simplify-0.0.6-8.el6ost.noarch openstack-puppet-modules-2014.1-20.2.el6ost.noarch Used the QE's username/password to verify. The deployment has completed successfully using the subscription manager. [root@<hostname> ~]# subscription-manager list +-------------------------------------------+ Installed Product Status +-------------------------------------------+ Product Name: Red Hat Enterprise Linux Server Product ID: 69 Version: 7.0 Arch: x86_64 Status: Subscribed Status Details: Starts: 02/21/2014 Ends: 02/21/2015 Product Name: Red Hat OpenStack Product ID: 191 Version: 5.0 Arch: x86_64 Status: Subscribed Status Details: Starts: 02/21/2014 Ends: 02/21/2015
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. http://rhn.redhat.com/errata/RHBA-2014-1090.html