In fact, foreman-proxy does not want to start anymore.
It just started once after the upgrade, and now, it fails with the already reported error.
···De : email@example.com [mailto:firstname.lastname@example.org] De la part de SCHAER Frederic Envoyé : jeudi 25 septembre 2014 19:05 À : email@example.com Objet : [PROVENANCE INTERNET] [foreman-users] foreman 1.6 puppet modules : /etc/foreman-proxy/settings.d
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 :
run!': private methodgsub’ called for false:FalseClass (NoMethodError)
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 :]
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 firstname.lastname@example.org:email@example.com.
To post to this group, send email to firstname.lastname@example.org:email@example.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.