Description of problem: After assigning a content view to a unmanaged, but registered host the puppet environment did not change. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Install Sat6 2. Create Product 3. Create puppet repository under that product 4. Import puppet module to the new repository 5. Create a new content view 6. Add the imported puppet module to the content view 7. Publish the content view 8. Install the consumer rpm to the Sat6 server located at http://hostname/pub 9. Register the Sat6 server to itself 10. In the UI, under content hosts, assign the new Sat6 server to the published content view Actual results: Click on 'Provisioning Details' and note that the puppet environment still shows 'production'. Expected results: The host record for the content host reflects the puppet environment from the content view. Additional info:
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
This issue was fixed as part of 1123959; therefore, going to close this one as a duplicate. *** This bug has been marked as a duplicate of bug 1123959 ***