Project

General

Profile

Actions

Feature #756

closed

Foreman doesn't see puppet environment's modulepath changes until restart

Added by Marcello de Sousa almost 14 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Category:
Importers
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I manage my modulepaths via puppet recipes. When they change, puppet sees it, but Foreman doesn't until I restart it.

As discussed with Ohad (on IRC) :

<marcellods> btw, is it normal that I have to restart foreman when a modulepath (from a puppet environment) changes  ?
< ohadlevy> marcellods: yeah, foreman reads puppet config upon initialization
< ohadlevy> marcellods: unless you run it via rake
< ohadlevy> it would take longer, but we can check if the modulepath changed
(...)
< ohadlevy> marcellods: ... i think that the rake task should detect it
< ohadlevy> marcellods: it should not detect it when you click on import from the ui


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #565: "rake puppet:import:puppet_classes" not detecting changes properlyClosedPaul Kelly01/04/2011Actions
Actions

Also available in: Atom PDF