This commit may also be useful in figuring out what has changed: https://github.com/puppetlabs/puppet/commit/0cea47ec90e77e81c27ffbedbd46bb5357a45d66 (it was part of this ticket: https://projects.puppetlabs.com/issues/14609)
The sample config.ru for puppet under rack was updated for Telly because of something that sounds a lot like what's happening here. HTH On Fri, Jul 6, 2012 at 12:18 PM, Eric Shamow <e...@puppetlabs.com> wrote: > Ohad, > > Without poking too deeply, the "Could not find value for $confdir" raises an > eyebrow - possible that you are referencing a global, which will be > deprecated in the next major release. You'll need to fully qualify scope: > > http://docs.puppetlabs.com/guides/scope_and_puppet.html > > This should be producing warnings in 2.7 and failing when the next major > release hits. > > -Eric > > -- > > Eric Shamow > Professional Services > http://puppetlabs.com/ > (c)631.871.6441 > > > On Friday, July 6, 2012 at 3:16 PM, Ohad Levy wrote: > >> >> >> On Wed, Jul 4, 2012 at 6:49 PM, pdpinfo <pdp...@tiscali.it >> (mailto:pdp...@tiscali.it)> wrote: >> > Hi all, >> > >> > just trying a lab with newest versions: >> > >> > - puppet-server: 3.0.0-0.1rc3.2 >> > - passenger: 3.0.12-1 >> > - foreman: 1.0.0-0.4 >> > >> > I hit problems with foreman 1.0 not able to work with Puppet 3.0. >> > >> > Foreman 1.0 worked correctly with puppet-server 2.7.17-1 (fresh-installed). >> > >> > Upgrading the package (from foreman-devel repo) to latest version, >> > Foreman service fails with error: >> > "... >> > /usr/lib/ruby/site_ruby/1.8/puppet/settings.rb:278:in `convert': Error >> > converting value for param 'hostcert': Error converting value for param >> > 'certdir': Error converting value for param 'ssldir': Could not find value >> > for $confdir (Puppet::Settings::InterpolationError) >> > ...." >> > >> > Any hints ? >> >> I'm guessing puppet internals changed a bit, mind opening an issue on >> foreman tracker ? >> as a work around, you could probably change >> lib/foreman/default_settings/loader.rb not to use Puppet settings.. >> >> Ohad >> > >> > Thank you >> > -- >> > You received this message because you are subscribed to the Google Groups >> > "Puppet Users" group. >> > To view this discussion on the web visit >> > https://groups.google.com/d/msg/puppet-users/-/qQ6yvf73SvUJ. >> > To post to this group, send email to puppet-users@googlegroups.com >> > (mailto:puppet-users@googlegroups.com). >> > To unsubscribe from this group, send email to >> > puppet-users+unsubscr...@googlegroups.com >> > (mailto:puppet-users%2bunsubscr...@googlegroups.com). >> > For more options, visit this group at >> > http://groups.google.com/group/puppet-users?hl=en. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to puppet-users@googlegroups.com >> (mailto:puppet-users@googlegroups.com). >> To unsubscribe from this group, send email to >> puppet-users+unsubscr...@googlegroups.com >> (mailto:puppet-users+unsubscr...@googlegroups.com). >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. > > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Users" group. > To post to this group, send email to puppet-users@googlegroups.com. > To unsubscribe from this group, send email to > puppet-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > -- Matthaus Litteken Release Manager, Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
