Project

General

Profile

Actions
Copy link

Bug #2206

closed

Puppet Classes' "New Puppetclass" form does not allow setting Environment

Added by Colin Hudler about 12 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Ohad Levy
Category:
Web Interface
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Steps to reproduce:

Navigate to More -> Configuration -> Puppetclasses and click on "New Puppetclass" green button. The new puppetclass form loads, but disables input for Puppet Environments.

What is expected:

The form loads and allows the user to (multi)select puppet environments that are associated with the puppet class.

Details:

This problem exists in the 1.1 stable release, but not previously. I understand that Foreman has the capability of automatically mapping classes to environments from the puppetmaster during import. This feature would not work for us as is; we're using the Classes purely for the filtering capability in the foreman UI.

Impact:

It is not possible to add manually created puppet classes to hosts, because foreman filters classes that are outside of the target's environment.

Actions
Copy link

Also available in: Atom PDF