Greetings,
I recently upgraded the vm that runs our puppet server which ended up
breaking puppet server. It seems that puppet server 1.0.1 and either
foreman-proxy 1.7 or 1.8 cause a problem with the puppet server.
I created an issue <https://tickets.puppetlabs.com/browse/SERVER-501> on
PuppetLabs but I seem to think it is a foreman issue not a PuppetLabs
issue. I have attached the error log of the puppet server. As you can
see, there are problems with ruby. I suspect that the foreman-proxy
installs ruby libs that conflict with puppet server.
Any help would be much appreciated.
Thanks
puppet_error_log.txt (17 KB)
I created a self contained vagrant environment that demonstrates the issue.
Can you please take a look?
https://github.com/Conzar/puppetserver_foremanproxy_error
···
On Tuesday, March 24, 2015 at 8:39:48 AM UTC+13, Michael Speth wrote:
>
> Greetings,
> I recently upgraded the vm that runs our puppet server which ended up
> breaking puppet server. It seems that puppet server 1.0.1 and either
> foreman-proxy 1.7 or 1.8 cause a problem with the puppet server.
>
> I created an issue on
> PuppetLabs but I seem to think it is a foreman issue not a PuppetLabs
> issue. I have attached the error log of the puppet server. As you can
> see, there are problems with ruby. I suspect that the foreman-proxy
> installs ruby libs that conflict with puppet server.
>
> Any help would be much appreciated.
>
> Thanks
>
Michael,
On Ubuntu 14.04 we make the package depend on ruby1.9.1 or
ruby-interpreter, from what I see in
https://apt.puppetlabs.com/dists/trusty/main/binary-amd64/Packages
puppetserver relies on JRuby solely and it only requires
ruby-interpreter as a side dependency, so there shouldn't be any
conflict. It says using it's own JRuby interpreter so it's isolated from
the system Ruby which is used for the smart-proxy.
I'll give it a go on the Vagrant machine, currently I don't have
Virtualbox. Why do you think the proxy is causing that?
Does puppetserver it work when you remove the smart-proxy package? Can
you also post the logs for 'puppetserver foreground --debug'
Thanks, I appreciate the effort put into the bug report
···
On 03/23, Michael Speth wrote:
> I created a self contained vagrant environment that demonstrates the issue.
> Can you please take a look?
>
> https://github.com/Conzar/puppetserver_foremanproxy_error
>
> On Tuesday, March 24, 2015 at 8:39:48 AM UTC+13, Michael Speth wrote:
> >
> > Greetings,
> > I recently upgraded the vm that runs our puppet server which ended up
> > breaking puppet server. It seems that puppet server 1.0.1 and either
> > foreman-proxy 1.7 or 1.8 cause a problem with the puppet server.
> >
> > I created an issue on
> > PuppetLabs but I seem to think it is a foreman issue not a PuppetLabs
> > issue. I have attached the error log of the puppet server. As you can
> > see, there are problems with ruby. I suspect that the foreman-proxy
> > installs ruby libs that conflict with puppet server.
> >
> > Any help would be much appreciated.
> >
> > Thanks
> >
>
> --
> 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 foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
–
Daniel Lobato Garcia
@eLobatoss
blog.daniellobato.me
daniellobato.me
GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
Keybase: https://keybase.io/elobato
Thank you for looking into this. I have attached the debug log.
puppetserver_forground_debug.txt (8.43 KB)
···
On Tuesday, March 24, 2015 at 8:42:42 PM UTC+13, Daniel Lobato wrote:
>
> Michael,
>
> On Ubuntu 14.04 we make the package depend on ruby1.9.1 or
> ruby-interpreter, from what I see in
> https://apt.puppetlabs.com/dists/trusty/main/binary-amd64/Packages
> puppetserver relies on JRuby solely and it only requires
> ruby-interpreter as a side dependency, so there shouldn't be any
> conflict. It says using it's own JRuby interpreter so it's isolated from
> the system Ruby which is used for the smart-proxy.
>
> I'll give it a go on the Vagrant machine, currently I don't have
> Virtualbox. Why do you think the proxy is causing that?
>
> Does puppetserver it work when you remove the smart-proxy package? Can
> you also post the logs for 'puppetserver foreground --debug'
>
>
> Thanks, I appreciate the effort put into the bug report
>
>
> On 03/23, Michael Speth wrote:
> > I created a self contained vagrant environment that demonstrates the
> issue.
> > Can you please take a look?
> >
> > https://github.com/Conzar/puppetserver_foremanproxy_error
> >
> > On Tuesday, March 24, 2015 at 8:39:48 AM UTC+13, Michael Speth wrote:
> > >
> > > Greetings,
> > > I recently upgraded the vm that runs our puppet server which ended
> up
> > > breaking puppet server. It seems that puppet server 1.0.1 and either
> > > foreman-proxy 1.7 or 1.8 cause a problem with the puppet server.
> > >
> > > I created an issue
> on
> > > PuppetLabs but I seem to think it is a foreman issue not a PuppetLabs
> > > issue. I have attached the error log of the puppet server. As you
> can
> > > see, there are problems with ruby. I suspect that the foreman-proxy
> > > installs ruby libs that conflict with puppet server.
> > >
> > > Any help would be much appreciated.
> > >
> > > Thanks
> > >
> >
> > --
> > 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 foreman-user...@googlegroups.com .
> > To post to this group, send email to forema...@googlegroups.com
> .
> > Visit this group at http://groups.google.com/group/foreman-users.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
> Daniel Lobato Garcia
>
> @eLobatoss
> blog.daniellobato.me
> daniellobato.me
>
> GPG: http://keys.gnupg.net/pks/lookup?op=get&search=0x7A92D6DD38D6DE30
> Keybase: https://keybase.io/elobato
>
