Project

General

Profile

Actions
Copy link

Bug #6302

closed

When Importing Puppet Classes, Broken Autoload Path's Ignored

Added by Dominic Cleal almost 10 years ago. Updated almost 5 years ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
Puppet
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Migrated from https://github.com/theforeman/foreman/issues/1527

1. Create file `profiles/manifests/a_profile.pp` on puppetmaster
2. Within the file define `class profiles::my_profile{...}`
3. Import classes from the puppet master

Result: Foreman finds and imports a class called `profiles::my_profile`, and allows it to be applied to hosts. When a host tries to access that class, puppet fails to autoload it because the path does not match the class name.

Expected: Best case, a warning about the broken paths and not letting it be imported. worst case, just not detecting it as a valid class to import.

Actions
Copy link
 #1

Updated by Ewoud Kohl van Wijngaarden almost 5 years ago

  • Status changed from New to Rejected

We're dropping Puppet 3 and only rely on the Puppet REST API. That means we no longer show any invalid classes

Actions
Copy link

Also available in: Atom PDF