Project

General

Custom queries

Profile

Actions
Copy link

Bug #15867

open

Changing puppet environment on the hostgroup page shows all puppet classes

Added by David Davis almost 9 years ago. Updated about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Puppet integration
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Steps to reproduce:

1. Create and publish two content views (View1 and View2) with two different sets of puppet modules
2. Create a Hostgroup and set it to one of the view's environments
3. Edit your Hostgroup and go to the Puppet Classes tab. Observe your view's puppet modules
4. Go back to Host Group tab and hit "Reset Puppet Environment to match selected Content View"
5. See the puppet classes and observe all puppet modules from BOTH content views

The problem is that we're not sending in hostgroup_id or environment_id so it creates a hostgroup without an environment here:

#2

Updated by David Davis almost 9 years ago

  • Project changed from Katello to Foreman
  • Subject changed from Hitting "Reset Puppet Environment to match selected Content View" on the hostgroup page shows different set of puppet classes even if env is unchanged to Changing puppet environment on the hostgroup page shows all puppet classes
#3

Updated by The Foreman Bot almost 9 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to David Davis
  • Pull request https://github.com/theforeman/foreman/pull/3680 added
#4

Updated by Dominic Cleal about 8 years ago

  • Category set to Puppet integration
  • Status changed from Ready For Testing to New
  • Assignee deleted (David Davis)
  • Pull request deleted (https://github.com/theforeman/foreman/pull/3680)
Actions
Copy link

Also available in: Atom PDF