Actions
Feature #756
closedForeman doesn't see puppet environment's modulepath changes until restart
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
Updated by Anonymous about 14 years ago
- Status changed from New to Ready For Testing
- % Done changed from 0 to 100
Updated by Ohad Levy about 14 years ago
- Status changed from Ready For Testing to Closed
- Assignee changed from Ohad Levy to Marcello de Sousa
Actions