Project

General

Profile

Actions

Bug #10392

closed

Foreman with Puppet: Puppet Classes can't be assigned to Config Groups

Added by Stefan Hölzle about 9 years ago. Updated about 9 years ago.

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

Description

Foreman version: 1.8.0

Steps to reproduce:
  1. Webinterface -> Configure -> Config groups
  2. New Config Group
  3. Puppet classes can't be assigned to config group

Files

config_groups.png View config_groups.png 32.5 KB Stefan Hölzle, 05/06/2015 11:11 AM
Screenshot from 2015-05-06 16_48_48.png View Screenshot from 2015-05-06 16_48_48.png 22.3 KB working installation Dominic Cleal, 05/06/2015 11:49 AM
Screenshot from 2015-05-07 11_57_07.png View Screenshot from 2015-05-07 11_57_07.png 69.9 KB class_edit.js Dominic Cleal, 05/07/2015 06:58 AM

Related issues 1 (0 open1 closed)

Related to Foreman - Bug #10393: Foreman with Puppet: Puppet Classes can't be assigned to hostsResolved05/06/2015Actions
Actions #1

Updated by Dominic Cleal about 9 years ago

  • Project changed from Website to Foreman
  • Category set to Puppet integration

I can't see an issue here, what precisely do you mean by you "can't"? You should see a list of modules and when you click the module, a plus icon to the right. Are you using an admin or non-admin account?

Actions #2

Updated by Dominic Cleal about 9 years ago

  • Related to Bug #10393: Foreman with Puppet: Puppet Classes can't be assigned to hosts added
Actions #3

Updated by Stefan Hölzle about 9 years ago

I attached a screenshot.
If I select an available class from the shown list by , I'd expect that it would be added to the included classes.
However nothing happens.

Actions #4

Updated by Dominic Cleal about 9 years ago

If you click on any of those blue "shared-*" headings, it should expand like my attachment, changes the "+" to a "-" and then shows a list of classes in black underneath. What happens if you click it?

If that isn't working, try opening your browser console (usually Ctrl+Shift+J) and try it again, paste/attach any messages from the console to this bug report along with the browser version, in case it's an error there.

Actions #5

Updated by Stefan Hölzle about 9 years ago

If I try to expand an item, nothing happens.
Browser console contains the following error for each time I click on one of the "shared-*" items: Uncaught ReferenceError: expandClassList is not defined
Nothing else in the log.

Browsers:
  • Chromium 42.0.2311.135 (64 bit)
  • Firefox 37.0.2 (64 bit)
Actions #6

Updated by Dominic Cleal about 9 years ago

Is this an upgrade or a clean installation?

Something looks wrong with how the page is rendering, probably a missing JavaScript file. On the Sources tab of your console you should see a class_edit.js file, did that download OK? It should contain expandClassList. (See attachment.) If not, the network tab may show an error?

Actions #7

Updated by Stefan Hölzle about 9 years ago

I initially installed foreman 1.7 from the sources: git clone https://github.com/theforeman/foreman.git -b 1.7-stable
After foreman 1.8 was released, I switched to 1.8-stable and followed the upgrade instructions: http://theforeman.org/manuals/1.8/index.html#3.6Upgrade
Before performing the upgrade procedure I executed bundler to install any new dependencies: bundle install --without prosgresql pg --path vendor

The class_edit.js file doesn't contain expandClassList.

I tried a clean installation from the 1.8-stable sources and the class_edit.js now contains expandClassList. The "shared-*" items are now expandable.
It seems this was an upgrade issue.
Thanks!

With a clean installation, issue #10393 does also not appear.

Actions #8

Updated by Dominic Cleal about 9 years ago

  • Status changed from New to Resolved

Possibly the assets weren't recompiled successfully, that's the bundle exec rake assets:precompile line.

Anyway, glad you sorted it!

Actions

Also available in: Atom PDF