Bug 1247625 - Selecting other hostgroup when creating new host does not update Puppet Environment
Summary: Selecting other hostgroup when creating new host does not update Puppet Envir...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-28 13:15 UTC by Maxim Burgerhout
Modified: 2021-03-11 14:22 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
edit hostgroup: puppet env does not change, cv does edit hostgroup: puppet classes screen now empty
Last Closed: 2017-01-11 19:36:53 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Maxim Burgerhout 2015-07-28 13:15:47 UTC
Description of problem:
Selecting a different hostgroup while creating a new host updates the content view, but it does not update the Puppet Environment.

Version-Release number of selected component (if applicable):
6.1.0 beta
foreman-1.7.2.32-1.el7sat.noarch

How reproducible:

Steps to Reproduce:
1. Open 'New Host' dialogue
2. Select Hostgroup A
3. Change that to Hostgroup B

Actual results:
Content view changes to the one belonging to Hostgroup B, Puppet Environment still reflects the Puppet Environment associated with the content view belonging to Hostgroup A

Expected results:
Both the content view and the Puppet Environment change to the default belonging to Hostgroup B

Additional info:

Comment 3 Bryan Kearney 2017-01-11 19:36:53 UTC
This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you believe doing so is an issue, please feel free to re-open and provide additional business information. Thank you.


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