OS version
Ruby version (/usr/bin/ruby -v)
Puppet version (puppet --version)
···
On 09/12/13 11:26, Jan-Frederic Markert wrote:
> Hey,
>
> I'm configuring a Ubuntu machine with foreman plus DNS + DHCP proxies.
>
> The first run of foreman-installer always gives me the following error:
>
> ...
> [DEBUG 2013-12-09 10:59:08 main]
> Service[foreman-proxy](provider=debian): Executing
> '/etc/init.d/foreman-proxy start'
> [ WARN 2013-12-09 10:59:08 main]
> /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]:
> Triggered 'refresh' from 1 events
> [DEBUG 2013-12-09 10:59:08 main]
> /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: The
> container Class[Foreman_proxy::Service] will propagate my refresh event
> [DEBUG 2013-12-09 10:59:08 main] Class[Foreman_proxy::Service]: The
> container Stage[main] will propagate my refresh event
> [ INFO 2013-12-09 10:59:08 main] Class[Foreman_proxy::Service]:
> Scheduling refresh of Class[Foreman_proxy::Register]
> [DEBUG 2013-12-09 10:59:08 main]
> Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
> is missing
> [DEBUG 2013-12-09 10:59:08 main]
> Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
> is missing
> [ERROR 2013-12-09 10:59:08 main] *Could not find a suitable
> provider for foreman_smartproxy*
> ...
>
>
> Subsequent runs do not show this error again.
>
> Unfortunately I can't find related information about the missing feature
> "foreman_api" or the unsuitable providers.
> Can someone ?
I started to have random ruby seg faults after the generated catalog went
to ~800k. For me this was because of puppetlabs-mcollectve module. After I
removed it all runs where ok again.
luni, 9 decembrie 2013, 13:26:39 UTC+2, Jan-Frederic Markert a scris:
···
>
> Hey,
>
> I'm configuring a Ubuntu machine with foreman plus DNS + DHCP proxies.
>
> The first run of foreman-installer always gives me the following error:
>
> ...
>> [DEBUG 2013-12-09 10:59:08 main]
>> Service[foreman-proxy](provider=debian): Executing
>> '/etc/init.d/foreman-proxy start'
>> [ WARN 2013-12-09 10:59:08 main]
>> /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: Triggered
>> 'refresh' from 1 events
>> [DEBUG 2013-12-09 10:59:08 main]
>> /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]: The container
>> Class[Foreman_proxy::Service] will propagate my refresh event
>> [DEBUG 2013-12-09 10:59:08 main] Class[Foreman_proxy::Service]: The
>> container Stage[main] will propagate my refresh event
>> [ INFO 2013-12-09 10:59:08 main] Class[Foreman_proxy::Service]:
>> Scheduling refresh of Class[Foreman_proxy::Register]
>> [DEBUG 2013-12-09 10:59:08 main]
>> Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api is
>> missing
>> [DEBUG 2013-12-09 10:59:08 main]
>> Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api is
>> missing
>> [ERROR 2013-12-09 10:59:08 main] *Could not find a suitable provider
>> for foreman_smartproxy*
>> ...
>
>
> Subsequent runs do not show this error again.
>
> Unfortunately I can't find related information about the missing feature
> "foreman_api" or the unsuitable providers.
> Can someone ?
>
> Thanks, Fredi
>
Ah, this helped. I think the issue is due to the version of Puppet, as
we install ruby-foreman_api during the Puppet run and then expect it to
be available immediately - only Puppet 2.7.20+ is capable of this.
For the RPMs, we added a package dependency to ensure this is available
before the Puppet run starts, so I've proposed the same for the debs:
Thanks for the report!
···
On 09/12/13 11:41, Jan-Frederic Markert wrote:
> Hey, here are the details:
>
> OS version
>
> Ubuntu 12.04
>
> Ruby version (/usr/bin/ruby -v)
>
> ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]
>
> Puppet version (puppet --version)
>
> 2.7.11
Notice:
/Stage[main]/Foreman_proxy::Config/File[/etc/foreman-proxy/settings.yml]/owner:
owner changed 'root' to 'foreman-proxy'
Notice:
/Stage[main]/Foreman_proxy::Config/File[/etc/foreman-proxy/settings.yml]/group:
group changed 'root' to 'foreman-proxy'
Notice: /Stage[main]/Foreman_proxy::Service/Service[foreman-proxy]/ensure:
ensure changed 'stopped' to 'running'
Error: Could not find a suitable provider for foreman_smartproxy
Notice: Finished catalog run in 1089.41 seconds
Looks entirely unrelated to me, that was an error loading the web UI.
Your default Ruby version on EL6 should always remain 1.8.7 (and Puppet
runs under this), but the Foreman UI runs under 1.9.3 via software
collections.
A few questions:
a) is rubygem-foreman_api installed?
b) does this print true? ruby -rrubygems -e "require 'foreman_api'; p true"
c) can you pastebin Puppet debug logs?
···
On 04/03/14 07:53, Luke Chavers wrote:
> Same issue here. We've been trying to figure this one out for a few
> days now.
>
> [luke@vagrant ~]# cat /etc/redhat-release
> CentOS release 6.4 (Final)
>
> [luke@vagrant ~]# puppet --version
> 3.4.3
>
> [luke@vagrant ~]# ruby --version
> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>
>
> I suspect that our ruby version of 1.8.7 may be to blame because of
> Dominic's solution
> here: https://groups.google.com/forum/#!topic/foreman-users/8yt4i6UzEog
> .. I cannot help but think those two are related.
···
Am Montag, 9. Dezember 2013 12:54:58 UTC+1 schrieb Dominic Cleal:
>
> On 09/12/13 11:41, Jan-Frederic Markert wrote:
> > Hey, here are the details:
> >
> > OS version
> >
> > Ubuntu 12.04
> >
> > Ruby version (/usr/bin/ruby -v)
> >
> > ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]
> >
> > Puppet version (puppet --version)
> >
> > 2.7.11
>
> Ah, this helped. I think the issue is due to the version of Puppet, as
> we install ruby-foreman_api during the Puppet run and then expect it to
> be available immediately - only Puppet 2.7.20+ is capable of this.
>
> For the RPMs, we added a package dependency to ensure this is available
> before the Puppet run starts, so I've proposed the same for the debs:
>
> https://github.com/theforeman/foreman-packaging/pull/145
>
> Thanks for the report!
>
> --
> Dominic Cleal
> Red Hat Engineering
>
I have the same error, but I'm on:
puppet-3.3.2
OS = OracleLinux 6.4
ruby = ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
rubygem-foreman_api-0.1.9-1.el6.noarch
When running puppet with debug I get the following:
Debug: Failed to load library 'foreman_api' for feature 'foreman_api'
Debug: Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
is missing
Debug: Failed to load library 'foreman_api' for feature 'foreman_api'
Debug: Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
is missing
Error: Could not find a suitable provider for foreman_smartproxy
Any idea why the error?
Best regards,
Cristian Falcas
luni, 9 decembrie 2013, 14:30:57 UTC+2, Jan-Frederic Markert a scris:
···
>
> Updating puppet did the trick, thanks!
>
> Am Montag, 9. Dezember 2013 12:54:58 UTC+1 schrieb Dominic Cleal:
>>
>> On 09/12/13 11:41, Jan-Frederic Markert wrote:
>> > Hey, here are the details:
>> >
>> > OS version
>> >
>> > Ubuntu 12.04
>> >
>> > Ruby version (/usr/bin/ruby -v)
>> >
>> > ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]
>> >
>> > Puppet version (puppet --version)
>> >
>> > 2.7.11
>>
>> Ah, this helped. I think the issue is due to the version of Puppet, as
>> we install ruby-foreman_api during the Puppet run and then expect it to
>> be available immediately - only Puppet 2.7.20+ is capable of this.
>>
>> For the RPMs, we added a package dependency to ensure this is available
>> before the Puppet run starts, so I've proposed the same for the debs:
>>
>> https://github.com/theforeman/foreman-packaging/pull/145
>>
>> Thanks for the report!
>>
>> --
>> Dominic Cleal
>> Red Hat Engineering
>>
>
My mistaken then. I have very little direct experience with Ruby
development, so I am a bit ignorant of all of it.
It will take me a little time to reset the machine so that I can execute
"b" before puppet's first run, but post-puppet it does return true:
[luke@vagrant ~]# ruby -rrubygems -e "require 'foreman_api'; p true"
true
I am also pretty sure that this error only occurs on the initial puppet
run, and not on subsequent runs, but I'll verify that as well and get a
full debug log.
As always, I appreciate your help Dominic. Since starting on my
adventure with Foreman you've been an incredible help.
Thanks,
Luke
···
> Looks entirely unrelated to me, that was an error loading the web UI.
> Your default Ruby version on EL6 should always remain 1.8.7 (and Puppet
> runs under this), but the Foreman UI runs under 1.9.3 via software
> collections.
>
> A few questions:
>
> a) is rubygem-foreman_api installed?
> b) does this print true? ruby -rrubygems -e "require 'foreman_api'; p true"
> c) can you pastebin Puppet debug logs?
>
Ah okay. What's meant to happen is that foreman_proxy::install will
install rubygem-foreman_api, but there's a Puppet "feature" in the
foreman module for this provider
(foreman/lib/puppet/feature/foreman_api.rb) which will detect when the
library is available.
i.e. Puppet will regularly attempt to load the foreman_api library
during the run, and once the package has been installed, it should succeed.
The only thing that comes to mind is the rubygems dependency (of
foreman_api), which for Puppet 2 RPMs isn't a dependency and for Puppet
3 it is, so in your case it should already be available and loaded.
I think debug logs will be the most useful thing next.
···
--
Dominic Cleal
Red Hat Engineering
On 04/03/14 13:14, Luke Chavers wrote:
My mistaken then. I have very little direct experience with Ruby
development, so I am a bit ignorant of all of it.
It will take me a little time to reset the machine so that I can execute
"b" before puppet’s first run, but post-puppet it does return true:
[luke@vagrant ~]# ruby -rrubygems -e "require 'foreman_api'; p true"
true
I am also pretty sure that this error only occurs on the initial puppet
run, and not on subsequent runs, but I’ll verify that as well and get a
full debug log.
As always, I appreciate your help Dominic. Since starting on my
adventure with Foreman you’ve been an incredible help.
Thanks,
Luke
Looks entirely unrelated to me, that was an error loading the web UI.
Your default Ruby version on EL6 should always remain 1.8.7 (and Puppet
runs under this), but the Foreman UI runs under 1.9.3 via software
collections.
A few questions:
a) is rubygem-foreman_api installed?
b) does this print true? ruby -rrubygems -e "require ‘foreman_api’; p true"
c) can you pastebin Puppet debug logs?
It works only if I install rubygem-foreman_api before running puppet
vineri, 10 ianuarie 2014, 13:18:44 UTC+2, Cristian Falcas a scris:
···
>
> Hi,
>
> I have the same error, but I'm on:
> puppet-3.3.2
> OS = OracleLinux 6.4
> ruby = ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
> rubygem-foreman_api-0.1.9-1.el6.noarch
>
>
> When running puppet with debug I get the following:
>
> Debug: Failed to load library 'foreman_api' for feature 'foreman_api'
> Debug: Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
> is missing
> Debug: Failed to load library 'foreman_api' for feature 'foreman_api'
> Debug: Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
> is missing
> Error: Could not find a suitable provider for foreman_smartproxy
>
>
> Any idea why the error?
>
> Best regards,
> Cristian Falcas
>
>
> luni, 9 decembrie 2013, 14:30:57 UTC+2, Jan-Frederic Markert a scris:
>>
>> Updating puppet did the trick, thanks!
>>
>> Am Montag, 9. Dezember 2013 12:54:58 UTC+1 schrieb Dominic Cleal:
>>>
>>> On 09/12/13 11:41, Jan-Frederic Markert wrote:
>>> > Hey, here are the details:
>>> >
>>> > OS version
>>> >
>>> > Ubuntu 12.04
>>> >
>>> > Ruby version (/usr/bin/ruby -v)
>>> >
>>> > ruby 1.8.7 (2011-06-30 patchlevel 352) [i686-linux]
>>> >
>>> > Puppet version (puppet --version)
>>> >
>>> > 2.7.11
>>>
>>> Ah, this helped. I think the issue is due to the version of Puppet, as
>>> we install ruby-foreman_api during the Puppet run and then expect it to
>>> be available immediately - only Puppet 2.7.20+ is capable of this.
>>>
>>> For the RPMs, we added a package dependency to ensure this is available
>>> before the Puppet run starts, so I've proposed the same for the debs:
>>>
>>> https://github.com/theforeman/foreman-packaging/pull/145
>>>
>>> Thanks for the report!
>>>
>>> --
>>> Dominic Cleal
>>> Red Hat Engineering
>>>
>>
Usually re-running it a few times gets past it, or downgrading the
version of Puppet (temporarily).
···
On 06/03/14 12:01, Luke Chavers wrote:
> I had to put this aside for a moment because of yet-another mind
> boggling problem:
>
> Debug:
> template[/venv/resources/puppet/modules/apache/templates/namevirtualhost.erb]:
> Bound template variables for
> /venv/resources/puppet/modules/apache/templates/namevirtualhost.erb
> in 0.00 seconds
> Debug:
> template[/venv/resources/puppet/modules/apache/templates/namevirtualhost.erb]:
> Interpolated template
> /venv/resources/puppet/modules/apache/templates/namevirtualhost.erb
> in 0.00 seconds
> /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/leaf.rb:117: [BUG]
> Segmentation fault
> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>
>
>
> So far 2014 has not been my year...
>
> I'll post the debug logs as soon as I'm able.
I changed my Vagrant .box to a CentOS 6.5 and that seg fault went away, at
least for now. I was using 6.4, and tried several vagrant boxes along
those lines… but all had some sort of error.
I do not know if this error is the same that I was receiving, given that I
changed my box. I was not receiving any of those errors or warnings
originally, and you'd think that they would show up, even with debug and
verbose off.
It looks like Puppet's trying to install the rubygem-foreman_api package
before EPEL is configured. rubygem-foreman_api has a dependency on
rubygem-rest-client (from EPEL).
It's not until about 3/4 of the way through that your yum::repo::epel
class configures EPEL itself.
Try adding a dependency so yum::repo::epel runs before
foreman_proxy::install, e.g.
Class['yum::repo::epel'] -> Class['foreman_proxy::install'] assuming the
EPEL class is well-contained.
···
On 06/03/14 15:25, Luke Chavers wrote:
> I changed my Vagrant .box to a CentOS 6.5 and that seg fault went away,
> at least for now. I was using 6.4, and tried several vagrant boxes
> along those lines.. but all had some sort of error.
>
> http://pastebin.com/eASbmShu
>
> I do not know if this error is the same that I was receiving, given that
> I changed my box. I was not receiving any of those errors or warnings
> originally, and you'd think that they would show up, even with debug and
> verbose off.
>
> It's all very weird... but I appreciate your help.
I'm hitting this pretty often at this point, even with Puppet 3.3.2. There
must be something particular to my setup that is causing it because I don't
think the community would tolerate this much failure…
Thanks,
Luke
···
On Thursday, March 6, 2014 6:12:46 AM UTC-6, Dominic Cleal wrote:
>
> On 06/03/14 12:01, Luke Chavers wrote:
> > I had to put this aside for a moment because of yet-another mind
> > boggling problem:
> >
> > Debug:
> >
> template[/venv/resources/puppet/modules/apache/templates/namevirtualhost.erb]:
>
> > Bound template variables for
> > /venv/resources/puppet/modules/apache/templates/namevirtualhost.erb
> > in 0.00 seconds
> > Debug:
> >
> template[/venv/resources/puppet/modules/apache/templates/namevirtualhost.erb]:
>
> > Interpolated template
> > /venv/resources/puppet/modules/apache/templates/namevirtualhost.erb
> > in 0.00 seconds
> > /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/leaf.rb:117: [BUG]
> > Segmentation fault
> > ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
> >
> >
> >
> > So far 2014 has not been my year...
> >
> > I'll post the debug logs as soon as I'm able.
>
> Ah, the segfault is no fun either. It seems to have started with Puppet
> 3.4, triggering some bug in Ruby.
>
> http://projects.theforeman.org/issues/4244 tracks it. Currently there
> are a couple of customer cases open with Red Hat, and a bugzilla open
> with engineering against ruby.
>
> *Usually* re-running it a few times gets past it, or downgrading the
> version of Puppet (temporarily).
>
> --
> Dominic Cleal
> Red Hat Engineering
>
That was a silly oversight on my part. EPEL is one of just a few things
that we do install prior to running puppet. When I changed boxes I made a
mistake when adding the rpm execution to the bootstrap script.
So, 500 errors and problems later, I've finally made it back to the point
of this whole thing:
I had to shave off the top to meet the pastebin 500k rule, so hopefully I
did not eliminate anything important.
Debug: Failed to load library 'foreman_api' for feature 'foreman_api'
Debug: Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
is missing
Debug: Logstash::Output::Tcp[logio-primary]: The container
Class[xxx::Profile::App::Logio::Stage_log] will propagate my refresh event
Debug: Class[xxx::Profile::App::Logio::Stage_log]: The container
Stage[main] will propagate my refresh event
Debug: Failed to load library 'foreman_api' for feature 'foreman_api'
Debug: Puppet::Type::Foreman_smartproxy::ProviderRest: feature foreman_api
is missing
Error: Could not find a suitable provider for foreman_smartproxy
This is from the very bottom of the log and is the first mention of
foreman_api failures. Everything else in our rather large configuration
executed perfectly, until we get to the very end.
Hopefully there is some hidden gem in there that tells you what is up,
because I'm entirely at a loss.
