Project

General

Profile

Actions

Bug #17502

closed

Foreman discovery proxy feature installation via puppet not working unless class is specified

Added by N V almost 8 years ago. Updated almost 8 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Hello,

The installation of the Foreman Discovery Proxy via Puppet does not work unless the class foreman_proxy::plugin::discovery is included explicitly. This is how my hiera config file for the host looks:

---
classes: [foreman_proxy, 'foreman_proxy::plugin::discovery']

foreman_proxy::dhcp: true
foreman_proxy::tftp: true
foreman_proxy::plugin::discovery::install_images: true
foreman_proxy::plugin::discovery: true

foreman_proxy::dhcp_managed: false
foreman_proxy::tftp_managed: true
foreman_proxy::puppet: false
foreman_proxy::puppetca: false

By "does not work" I mean the puppetrun will work, but won't actually setup the necessary to make discovery work (no fdi image download, no ruby-foreman-discovery package installation, no smart proxy config).

Foreman 1.13.2, Ubuntu 16.04.

Actions

Also available in: Atom PDF