Bug 1103248 - Puppet environment not set after assigning a content view
Summary: Puppet environment not set after assigning a content view
Keywords:
Status: CLOSED DUPLICATE of bug 1123959
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-30 14:23 UTC by Eric Helms
Modified: 2014-08-28 19:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-28 19:52:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Eric Helms 2014-05-30 14:23:11 UTC
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:

Comment 1 RHEL Program Management 2014-05-30 14:24:50 UTC
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.

Comment 3 Brad Buckingham 2014-08-28 19:52:50 UTC
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 ***


Note You need to log in before you can comment on or make changes to this bug.