2016-07-14 14:23 GMT+02:00 Roger Martensson <[email protected]>:
> > > 2016-07-14 14:16 GMT+02:00 Dominic Cleal <[email protected]>: > >> On 14/07/16 13:05, Roger Martensson wrote: >> > >> >> Did notice one more thing. The foreman-reports ruby-file didn't seem >> to >> > be installed when running foreman-installer. should it? >> > It was easy to fix but I believe that the foreman-installer used to do >> this? >> >> It still does, it should be installed to >> /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb >> when using Puppet Server. >> >> > In my case it didn't get installed at all. I had to manually install it > in the reports directory.. Then it started to work again. > (This was after running the "puppet 4-upgrade-foreman-installer) > > When I upgraded my production environment I noticed that foreman.rb-reports was inserted. So I guess something wasn't right with my test environment. What I did notice with both my environments was that I needed to change the paths found in /etc/sudoers.d/foreman-proxy. -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
