Foreman doesn't see puppet environment's modulepath changes until restart
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
#1 Updated by Marcello de Sousa over 9 years ago
As discussed while testing Bug #565: if Foreman is not restarted, changes in the environment configuration (new environment, change in modulepaths,etc) won't be seen.
This was creating a strange effect here:
- A new environment was created and imported via rake import task (the task sees the changes)
- Then on the GUI another a user trying to import a new class would see that environment as obsolete.
So, it would be nice if Foreman could always see changes in the puppet config without the need to restart it (like the rake task does).