facter-1.7.3 and puppet-3.3.1 on OS X Mavericks 10.9

[Paul Tötterman]

Hi,

Is anyone else getting this:

$ facter
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': cannot load such file -- facter/application (LoadError)
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'
from /usr/bin/facter:72:in `<main>'

$ puppet
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require': cannot load such file -- puppet/util/command_line (LoadError)
from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:45:in `require'
from /usr/bin/puppet:3:in `<main>'

Both installed from packages which were downloaded from http://downloads.puppetlabs.com/mac/

Cheers,

Paul

[Hannes Juutilainen]

It's the same issue as this: https://projects.puppetlabs.com/issues/18205

It seems to be fixed already but not included in the current release version. Building Puppet and Facter from source resolves this issue so I'd expect it to be fixed in near future.

--

Hannes Juutilainen

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0f6bf066-6afd-4db5-8ab1-c6db16afc457%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Paul Tötterman]

It's the same issue as this: https://projects.puppetlabs.com/issues/18205

Thank you for digging it up for me. Somehow google just failed me.

 

It seems to be fixed already but not included in the current release version. Building Puppet and Facter from source resolves this issue so I'd expect it to be fixed in near future.

Are you saying that no official released packages from PuppetLabs work on OS X 10.9? And the fix is to be released on Puppet 3.4.0? For which no release date is set and there seems to be at least 3.3.2 before 3.4.0 will come out.

Cheers,
Paul 

[Hannes Juutilainen]

I don't know anything about the release plan or schedule (perhaps someone from Puppet Labs could chime in)… Looks bad though: https://projects.puppetlabs.com/issues/21868

—

Hannes

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e86bff0a-72e1-4dc8-a1a2-6878f27b4dc3%40googlegroups.com.

[Khoury]

Does anyone know what the status is on Mavericks support? Has anyone tested it? It's been a while since the public release and Apple's policy of forcing new Macs to use Mavericks puts is in a tight spot if we can't get Puppet support for the OS. 

Thanks,

Khoury

[Jeff Bachtel]

I don't have a Maverick box to test on, but the PRs in question are applied to the 3.4.0 and onward tags, so I would bet that current OS X packages would do the right thing and work with the Ruby 2.0 on Maverick.

Jeff

On 01/14/2014 01:15 PM, Khoury wrote:

Does anyone know what the status is on Mavericks support? Has anyone tested it? It's been a while since the public release and Apple's policy of forcing new Macs to use Mavericks puts is in a tight spot if we can't get Puppet support for the OS.�

Thanks,

Khoury

On Friday, November 1, 2013 7:52:24 AM UTC-7, Hannes Juutilainen wrote:

I don't know anything about the release plan or schedule (perhaps someone from Puppet Labs could chime in)� Looks bad though:�https://projects.puppetlabs.com/issues/21868

�

Hannes

On 1.11.2013, at 15.16, Paul T�tterman <paul.to...@gmail.com> wrote:

It's the same issue as this:�https://projects.puppetlabs.com/issues/18205

Thank you for digging it up for me. Somehow google just failed me.

�

It seems to be fixed already but not included in the current release version. Building Puppet and Facter from source resolves this issue so I'd expect it to be fixed in near future.

Are you saying that no official released packages from PuppetLabs work on OS X 10.9? And the fix is to be released on Puppet 3.4.0? For which no release date is set and there seems to be at least 3.3.2 before 3.4.0 will come out.

Cheers,
Paul�

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e86bff0a-72e1-4dc8-a1a2-6878f27b4dc3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/68a1f653-66ec-4c31-bfe9-7e5ad7d01426%40googlegroups.com.

[Khoury Brazil]

That's good to hear. But I'm still concerned about Facter. Correct me if I'm wrong, but this issue indicates that Facter 1.7.5 will be targeted but we're currently on 1.7.4:

https://projects.puppetlabs.com/issues/22107

Did it make it into 1.7.4? 

On Tue, Jan 14, 2014 at 11:05 AM, Jeff Bachtel <jbac...@bericotechnologies.com> wrote:

I don't have a Maverick box to test on, but the PRs in question are applied to the 3.4.0 and onward tags, so I would bet that current OS X packages would do the right thing and work with the Ruby 2.0 on Maverick.

Jeff

On 01/14/2014 01:15 PM, Khoury wrote:

Does anyone know what the status is on Mavericks support? Has anyone tested it? It's been a while since the public release and Apple's policy of forcing new Macs to use Mavericks puts is in a tight spot if we can't get Puppet support for the OS. 

Thanks,

Khoury

On Friday, November 1, 2013 7:52:24 AM UTC-7, Hannes Juutilainen wrote:

I don't know anything about the release plan or schedule (perhaps someone from Puppet Labs could chime in)… Looks bad though: https://projects.puppetlabs.com/issues/21868

—

Hannes

On 1.11.2013, at 15.16, Paul Tötterman <paul.to...@gmail.com> wrote:

It's the same issue as this: https://projects.puppetlabs.com/issues/18205

Thank you for digging it up for me. Somehow google just failed me.

 

It seems to be fixed already but not included in the current release version. Building Puppet and Facter from source resolves this issue so I'd expect it to be fixed in near future.

Are you saying that no official released packages from PuppetLabs work on OS X 10.9? And the fix is to be released on Puppet 3.4.0? For which no release date is set and there seems to be at least 3.3.2 before 3.4.0 will come out.

Cheers,
Paul 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e86bff0a-72e1-4dc8-a1a2-6878f27b4dc3%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/68a1f653-66ec-4c31-bfe9-7e5ad7d01426%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52D58A95.1090308%40bericotechnologies.com.

[Matthaus Owens]

It didn't make it into Facter 1.7.4, but it will be in Facter 1.7.5, which should be entering RC soon.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAAqoMCYta6Dp684oYbEH3_Kd204%2BiWdzHd3S7n5MCA7CixWUdQ%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

--
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2014, September 23-24 in San Francisco

[Martijn]

facter-1.7.4-rc1 is available and it looks like it works!

Martijn

Op woensdag 30 oktober 2013 17:50:59 UTC+1 schreef Paul Tötterman:

[Paul Tötterman]

> facter-1.7.4-rc1 is available and it looks like it works!

Actually, it wasn't until 1.7.5 that the packages available from
downloads.puppetlabs.com were fixed, but it really seems to work now.

However, I have a problem with puppet on OS X 10.9. I'm using the
latest packaged version 3.4.2.

It may be a problem with the ruby and openssl configuration shipped
with OS X 10.9, but I'm getting:

Info: Creating a new SSL key for $fqdn
Error: Could not request certificate: SSL_connect returned=1 errno=0
state=SSLv2/v3 read server hello A: (null)
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/net/http.rb:918:in
`connect'

when running `puppet agent --test --verbose --debug --evaltrace --trace`.

There are some results on the web about ruby failing because of a
missing CA cert bundle, but the puppet master generated CA cert
wouldn't be included anyway, so that isn't a solution in this case.

Anyone have any other ideas?

Cheers,
Paul

[Matthaus Owens]

Paul, that ssl error looks like the following post on puppet-users: https://groups.google.com/forum/#!topic/puppet-users/4-6EimF_-NY/discussion, which relates to SNI. Adding a server alias to your puppetmaster vhost may resolve your problem. This is a change in ruby after 1.9.0, so it wouldn't have been in system ruby on OSX before mavericks.

HTH

Cheers,
Paul

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CANPS_M5vfAkAuTiytEG_GkB3XckAzk-kGXGXKPzix7CHAQ9uoA%40mail.gmail.com.

For more options, visit https://groups.google.com/groups/opt_out.

[Paul Tötterman]

Paul, that ssl error looks like the following post on puppet-users: https://groups.google.com/forum/#!topic/puppet-users/4-6EimF_-NY/discussion, which relates to SNI.

Thank you for pointing me in the right direction.

 

Adding a server alias to your puppetmaster vhost may resolve your problem. This is a change in ruby after 1.9.0, so it wouldn't have been in system ruby on OSX before mavericks.

I can run the agent with --server puppet.$domain or by setting the server in the config file. But I had no success in adding aliases to my puppet/passenger/apache config. After trying to add the required apache directives (NameVirtualHost, ServerName and ServerAlias) and restarting apache, no puppet agents would communicate properly with the master.

So I guess I'm going to go with server in puppet.conf for now.

Thanks,

Paul

[Brian Auron]

Hello,

I came looking for this exact error, but specifying "--server puppetmaster.domain" or setting "server = puppetmaster.domain" in puppet.conf doesn't allow a successful run of puppet. The error is the same as Paul had above:

Error: Could not request certificate: SSL_connect returned=1 errno=0 state=SSLv2/v3 read server hello A: (null)

But `openssl s_client -connect puppetmaster.domain:8140` works just fine. There are no DNS alternative names and we only have one puppetmaster. Does anybody have an idea? Thanks!

-Brian

[Oz DiGennaro]

I have installed version 2.0.0 from source.  I saw the same error.  But running ./install.rb fixed it!
Oz

[keith....@gmail.com]

Initially had this error, currently running factor 1.7.6 and puppet 3.6.2. fixed the ruby issue on the puppetmaster end (fedora 19) added foreman(1.6), been stable since Aug. OSX 10.9.5 currently no issues with puppet

hth
Keith