Project

General

Profile

Actions
Copy link

Bug #2206

closed

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

Added by Colin Hudler over 11 years ago. Updated about 10 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
 #1

Updated by Joerg Mauer about 11 years ago

We also require puppetclasses to be created manually and assigned to environments, which is no longer possible in 1.1.
I reverted part of f8d946082 and was able to recover the old behaviour:

 index ec060df..28ea691 100644
 --- a/app/views/puppetclasses/_form.html.erb
 +++ b/app/views/puppetclasses/_form.html.erb
 @@ -12,7 +12,7 @@

      <div class="tab-pane active form-horizontal" id="primary">
        <%= text_f f, :name %>
 -      <%= text_f f, :environments, :value => @puppetclass.environments.to_sentence, :class=>'span4', :label=> 'Puppet Environments', :disabled => true %>
 +      <%= multiple_checkboxes f, :environments, @puppetclass, Environment, :label => "Puppet Environments" %>
        <%= multiple_checkboxes f, :hostgroups,   @puppetclass, Hostgroup,   :label => "Hostgroups" %>
      </div>

Basic testing has been successfull so far.
I´d really appreciate if manually assigning puppetclasses to environments would still be possible in the future.

Actions
Copy link
 #2

Updated by Benjamin Papillon about 10 years ago

  • Description updated (diff)
  • Status changed from New to Rejected

Hi,

The decision has been made to always use smart proxy as the source of truth to manage puppet classes on Foreman.
Therefore this bug has been set to rejected.
Sorry guys I was in the same situation before migrating to smart proxy.

Regards,

Actions
Copy link

Also available in: Atom PDF