Project

General

Profile

Actions

Bug #7490

open

Foreman does not check for Environment match when assigning Host to HostGroup

Added by Jeff Sault over 10 years ago. Updated about 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

You can assign a Host to a HostGroup where the environment on each is different. When the Puppet agent runs, it ignores the configuration from the HostGroup.

Example:
1. Ensure that a class (e.g. puppetlabs-ntp) is in the 'development' environment and NOT in the 'production' environment.
2. Create a HostGroup in the 'development' environment. Assign the class from Step 1 to it, and optionally provide configuration details.
3. Create a new Host in the 'production' environment, and assign the HostGroup created in step 2 to the new host.
4. Run the puppet agent on the new Host.

Expected Results ================
An error is displayed at step 3, saying that the HostGroup is not compatible.

Actual Results ==============
No error is displayed. No software is installed by the puppet agent when it runs.


Related issues 2 (0 open2 closed)

Related to Foreman - Bug #5105: default Setting['remove_classes_not_in_environment'] to true and have class_selection partial show/hide inherited classes from parent based on this settingClosedJoseph MagenActions
Has duplicate Foreman - Feature #14717: Classes assigned to a parent hostgroup that are not avaliable to a given host should be indicated in the WebUIDuplicate04/19/2016Actions
Actions

Also available in: Atom PDF