Project

General

Profile

Actions

Bug #19495

closed

Inherit allowable template combinations in child host groups

Added by Iain Hallam about 7 years ago. Updated about 7 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I moved a server recently from a host group to a child host group, and its provisioning template changed. On digging it seems that the combinations that can be set for host group and environment on the Association page of the template editor aren't inherited, and don't propagate to any host groups under the selected group.

This surprised both me and ikonia on IRC. It seems that a tree structure should apply higher level choices to the lower levels, instead of having to define every new host group as a valid combination. This is what happens with Puppet classes, for instance.

I suppose changing the default at this stage might break a lot of configurations out in the wild, so perhaps there ought to be an install-wide setting for this, or simply a checkbox next to each combination to decide whether to apply to child host groups as well as the specified one.


Related issues 1 (1 open0 closed)

Is duplicate of Foreman - Bug #14624: Associating a template with a host group does not associate child host groupsNew04/13/2016Actions
Actions #1

Updated by Dominic Cleal about 7 years ago

  • Is duplicate of Bug #14624: Associating a template with a host group does not associate child host groups added
Actions #2

Updated by Dominic Cleal about 7 years ago

  • Status changed from New to Duplicate

Thanks for the report, this appears to be tracked as issue #14624.

Actions #3

Updated by Iain Hallam about 7 years ago

Dominic Cleal wrote:

Thanks for the report, this appears to be tracked as issue #14624.

So 'tis. I didn't find that one.

Actions

Also available in: Atom PDF