Hi,
I just attempted a migration from foreman 1.4.5 to 1.6.0 : I upgraded the foreman modules to the 1.6 version, and I had to create the settings.d directory manually for the puppet configuration to work correctly (I'm not using the foreman installer outside of puppet).
Since this dir was manually created, I did not chown the dir to the foreman-user, and this apparently prevented the foreman-proxy from starting, with this cryptic error displayed :
/usr/share/foreman-proxy/bin/…/lib/sinatra-patch.rb:22:in run!': private methodgsub' called for false:FalseClass (NoMethodError)
from /usr/share/foreman-proxy/bin/smart-proxy:44
Was this expected ?
Shouldn't the settings.d directory be managed either by the RPMs or the puppet modules ?
Appart from that, upgrade went smoothly , thanks for the great work :]
regards