Foreman-proxy 1.15 + Puppet 4.8.x

MK1 · July 10, 2017, 8:48pm

Hi,

I'm testing Foreman 1.15 to work with Puppet 4.8.x in particularly on
Debian 9 (stretch) which was released few weeks back, Puppet 4.8.2 is the
version shipped with Debian 9.
both Foreman+Puppet reside on the same box (all-in-one configuration),
seems to have got it up and run, until I tried to import the puppet classes
to Foreman,
it does not find the environments along with the Puppet classes.

Followed instruction
on Foreman :: Manual, I had
following ocnfigured:

(./setting.d/puppet.yml)
:enabled: https
:puppet_version: 4.8.2

(/etc/puppet/auth.conf)
path /puppet/v3/environments
method find
allow *

path /puppet/v3/environment_classes
method find
allow *

path /puppet/v3/resource_type
method search
allow *

(/etc/foreman-proxy/setting.d/puppet_proxy_legacy.yml)
:puppet_conf: /etc/puppet/puppet.conf
:puppet_url: https://playbox.cs.nsls2.local:8140

Started debugging both Foreman-proxy as well as the Puppet Master, when
foreman-proxy is trying to find the environments, production.log says:

···

------------------------------------------------ E, [2017-07-10T16:18:56.142122 ] ERROR -- : Error while retrieving puppet classes for 'production' environment D, [2017-07-10T16:18:56.142231 ] DEBUG -- : Could not find environment 'production' (Proxy::Puppet::EnvironmentNotFound) /usr/share/foreman-proxy/modules/puppet_proxy_puppet_api/v3_api_request.rb:27:in `list_classes' /usr/share/foreman-proxy/modules/puppet_proxy_puppet_api/v3_environment_classes_api_classes_retriever.rb:81:in `block in async_get_classes' /usr/lib/ruby/vendor_ruby/concurrent/executor/safe_task_executor.rb:24:in `block in execute' /usr/lib/ruby/vendor_ruby/concurrent/synchronization/mri_lockable_object.rb:38:in `block in synchronize' /usr/lib/ruby/vendor_ruby/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /usr/lib/ruby/vendor_ruby/concurrent/synchronization/mri_lockable_object.rb:38:in `synchronize' /usr/lib/ruby/vendor_ruby/concurrent/executor/safe_task_executor.rb:19:in `execute' /usr/lib/ruby/vendor_ruby/concurrent/promise.rb:526:in `block in realize' /usr/lib/ruby/vendor_ruby/concurrent/executor/ruby_thread_pool_executor.rb:333:in `run_task' /usr/lib/ruby/vendor_ruby/concurrent/executor/ruby_thread_pool_executor.rb:322:in `block (3 levels) in create_worker' /usr/lib/ruby/vendor_ruby/concurrent/executor/ruby_thread_pool_executor.rb:305:in `loop' /usr/lib/ruby/vendor_ruby/concurrent/executor/ruby_thread_pool_executor.rb:305:in `block (2 levels) in create_worker' /usr/lib/ruby/vendor_ruby/concurrent/executor/ruby_thread_pool_executor.rb:304:in `catch' /usr/lib/ruby/vendor_ruby/concurrent/executor/ruby_thread_pool_executor.rb:304:in `block in create_worker' E, [2017-07-10T16:18:56.204027 ] ERROR -- : Error while retrieving puppet classes for 'common' environment D, [2017-07-10T16:18:56.204108 ] DEBUG -- : Could not find environment 'common' (Proxy::Puppet::EnvironmentNotFound) /usr/share/foreman-proxy/modules/puppet_proxy_puppet_api/v3_api_request.rb:27:in `list_classes' /usr/share/foreman-proxy/modules/puppet_proxy_puppet_api/v3_environment_classes_api_classes_retriever.rb:81:in `block in async_get_classes' ............ (skip the repeatedly lines) -----------

Puppet debug logged:

Jul 10 16:18:56 playbox puppet-master[18102]: Routes Registered:
Jul 10 16:18:56 playbox puppet-master[18102]: Route /^/puppet//
Jul 10 16:18:56 playbox puppet-master[18102]: Route /^/puppet-ca//
Jul 10 16:18:56 playbox puppet-master[18102]: Route /./
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/^/puppet//
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/v3/
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/^/environments$/
Jul 10 16:18:56 playbox puppet-master[18102]: Did not match path
("/environment_classes")
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/^/environment/[^/]+$/
Jul 10 16:18:56 playbox puppet-master[18102]: Did not match path
("/environment_classes")
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/./
Jul 10 16:18:56 playbox puppet-master[18102]: Not Found: Could not find
indirection 'environment_classe’
Jul 10 16:18:56 playbox puppet-master[18102]: Handling request: GET
/puppet/v3/environment_classes?environment=production
Jul 10 16:18:56 playbox puppet-master[18102]: Routes Registered:
Jul 10 16:18:56 playbox puppet-master[18102]: Route /^/puppet//
Jul 10 16:18:56 playbox puppet-master[18102]: Route /^/puppet-ca//
Jul 10 16:18:56 playbox puppet-master[18102]: Route /./
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/^/puppet//
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/v3/
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/^/environments$/
Jul 10 16:18:56 playbox puppet-master[18102]: Did not match path
("/environment_classes")
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/^/environment/[^/]+$/
Jul 10 16:18:56 playbox puppet-master[18102]: Did not match path
("/environment_classes")
Jul 10 16:18:56 playbox puppet-master[18102]: Evaluating match for Route
/./
Jul 10 16:18:56 playbox puppet-master[18102]: Not Found: Could not find
indirection 'environment_classe’
Jul 10 16:18:56 playbox puppet-master[18102]: Handling request: GET
/puppet/v3/environment_classes?environment=common

Did someone have the same experience before? Could this be potential puppet
bug ?
Thanks.
MK

mmoll · July 10, 2017, 9:07pm

Hi,

···

On Mon, Jul 10, 2017 at 01:48:21PM -0700, MK wrote: > I'm testing Foreman 1.15 to work with Puppet 4.8.x in particularly on > Debian 9 (stretch) which was released few weeks back, Puppet 4.8.2 is the > version shipped with Debian 9. > both Foreman+Puppet reside on the same box (all-in-one configuration), > seems to have got it up and run, until I tried to import the puppet classes > to Foreman, > it does not find the environments along with the Puppet classes.

See Bug #19979: Puppet Integration with non-puppetserver Puppet 4.x broken - Smart Proxy - Foreman

Michael Moll

MK1 · July 11, 2017, 2:44pm

Thanks for the URL! My next approach was actually to install Puppet version
from puppetlab repo but unfortunately it's not available at this point yet.
Glad to see someone is using Foreman on Debian Stretch! Please feel free to
share your thoughts or anything…

MK

···

On Mon, Jul 10, 2017 at 5:07 PM, Michael Moll wrote:

Hi,

On Mon, Jul 10, 2017 at 01:48:21PM -0700, MK wrote:

I’m testing Foreman 1.15 to work with Puppet 4.8.x in particularly on
Debian 9 (stretch) which was released few weeks back, Puppet 4.8.2 is the
version shipped with Debian 9.
both Foreman+Puppet reside on the same box (all-in-one configuration),
seems to have got it up and run, until I tried to import the puppet
classes
to Foreman,
it does not find the environments along with the Puppet classes.

See Bug #19979: Puppet Integration with non-puppetserver Puppet 4.x broken - Smart Proxy - Foreman

Michael Moll

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/dgFKp1fDxBE/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

mmoll · July 11, 2017, 3:03pm

Hi,

···

On Tue, Jul 11, 2017 at 10:44:43AM -0400, mizuki wrote: > Thanks for the URL! My next approach was actually to install Puppet version > from puppetlab repo but unfortunately it's not available at this point yet. > Glad to see someone is using Foreman on Debian Stretch! Please feel free to > share your thoughts or anything... :)

Foreman and its components are working fine on Debian/stretch, we do
have nightly builds and are waiting for PuppetLabs’ packages ourselves,
as these are needed for a potential 1.16 release.

Regards

Michael Moll

MK1 · July 11, 2017, 3:43pm

I noticed, the nightly version works but not stable version just yet. We
are looking forward to have PuppetLab's packages to work with Foreman.

We stuck in the v3 world, with Stretch coming out, we have no choice but to
upgrade Puppet/Foreman for better support.

What puppetlab claims though, puppetserver will be the future version to be
and the current one will be obsoleted, is Foreman going to support
puppetserver? Would it be potentially included in 1.16 release as well?

Thanks so much!

MK

···

On Tue, Jul 11, 2017 at 11:03 AM, Michael Moll wrote:

Hi,

On Tue, Jul 11, 2017 at 10:44:43AM -0400, mizuki wrote:

Thanks for the URL! My next approach was actually to install Puppet
version
from puppetlab repo but unfortunately it’s not available at this point
yet.
Glad to see someone is using Foreman on Debian Stretch! Please feel free
to
share your thoughts or anything…

Foreman and its components are working fine on Debian/stretch, we do
have nightly builds and are waiting for PuppetLabs’ packages ourselves,
as these are needed for a potential 1.16 release.

Regards

Michael Moll

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/dgFKp1fDxBE/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

mmoll · July 11, 2017, 3:56pm

Hi,

···

On Tue, Jul 11, 2017 at 11:43:06AM -0400, mizuki wrote: > What puppetlab claims though, puppetserver will be the future version to be > and the current one will be obsoleted, is Foreman going to support > puppetserver? Would it be potentially included in 1.16 release as well?

Puppetserver is supported since Foreman 1.12 and 1.16 will also fully
support Puppetserver 5 (nightlies already do).

Regards

Michael Moll

MK1 · July 11, 2017, 6:35pm

Great! I will keep that in mind.

···

On Tue, Jul 11, 2017 at 11:56 AM, Michael Moll wrote:

Hi,

On Tue, Jul 11, 2017 at 11:43:06AM -0400, mizuki wrote:

What puppetlab claims though, puppetserver will be the future version to
be
and the current one will be obsoleted, is Foreman going to support
puppetserver? Would it be potentially included in 1.16 release as well?

Puppetserver is supported since Foreman 1.12 and 1.16 will also fully
support Puppetserver 5 (nightlies already do).

Regards

Michael Moll

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/foreman-users/dgFKp1fDxBE/unsubscribe.
To unsubscribe from this group and all its topics, 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 https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.