Puppet 4 support for reporting and ENC

Hey all,

Are there any timelines or milestones to puppet 4 support on foreman yet?
I'm using puppet 4 right now and having to deploy foreman on top of it will
be sweet. I've tried installing the packages manually and configure it but
it all fails on the rake commands.

OS: Debian 7
Puppetserver: 2.1 (installed via apt)
Foreman: 1.8 (installed via apt: foreman, foreman-postgresql)
PuppetDB: 2.3.5

I've symlinked all the binaries from /opt/puppetlabs/bin to /usr/bin hoping
it'll help but I get the error below when trying to setup the database

~ # foreman-rake --trace db:migrate
rake aborted!
LoadError: cannot load such file – facter
/usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in
require' /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:inblock in require'
/usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in
load_dependency' /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:inrequire'
/usr/share/foreman/lib/tasks/reset_permissions.rake:1:in <top (required)>' /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:inload'
/usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in
block in load' /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:inload_dependency'
/usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in
load' /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:inblock in load_tasks'
/usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:in
each' /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:inload_tasks'
/usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/application.rb:145:in
load_tasks' /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/railtie/configurable.rb:30:inmethod_missing'
/usr/share/foreman/Rakefile:7:in <top (required)>' /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:inload'
/usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in
load_rakefile' /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:689:inraw_load_rakefile'
/usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:94:in
block in load_rakefile' /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:176:instandard_exception_handling'
/usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:93:in
load_rakefile' /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:77:inblock in run'
/usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:176:in
standard_exception_handling' /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:75:inrun'
/usr/bin/rake:27:in `<main>'

Hope someone can point me out to the right direction. I'm willing to build
from the nightly as well.

> Hey all,
>
> Are there any timelines or milestones to puppet 4 support on foreman yet?
> I'm using puppet 4 right now and having to deploy foreman on top of it will
> be sweet. I've tried installing the packages manually and configure it but
> it all fails on the rake commands.

We're following Puppet 4 support on this tracker
http://projects.theforeman.org/issues/8447

For the moment it's not supported, but if you make it work it'd be great
to hear from you and get any patches you had to apply :slight_smile:

··· On 06/11, Choon Ming Goh wrote: > > OS: Debian 7 > Puppetserver: 2.1 (installed via apt) > Foreman: 1.8 (installed via apt: foreman, foreman-postgresql) > PuppetDB: 2.3.5 > > I've symlinked all the binaries from /opt/puppetlabs/bin to /usr/bin hoping > it'll help but I get the error below when trying to setup the database > > ~ # foreman-rake --trace db:migrate > rake aborted! > LoadError: cannot load such file -- facter > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > `require' > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > `block in require' > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in > `load_dependency' > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > `require' > /usr/share/foreman/lib/tasks/reset_permissions.rake:1:in `' > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in > `load' > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in > `block in load' > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in > `load_dependency' > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in > `load' > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:in > `block in load_tasks' > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:in > `each' > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:in > `load_tasks' > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/application.rb:145:in > `load_tasks' > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/railtie/configurable.rb:30:in > `method_missing' > /usr/share/foreman/Rakefile:7:in `' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in > `load' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in > `load_rakefile' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:689:in > `raw_load_rakefile' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:94:in > `block in load_rakefile' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:176:in > `standard_exception_handling' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:93:in > `load_rakefile' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:77:in > `block in run' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:176:in > `standard_exception_handling' > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:75:in > `run' > /usr/bin/rake:27:in `' > > Hope someone can point me out to the right direction. I'm willing to build > from the nightly as well. > > > > -- > 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

Looks like all the issue on class and environment import has been fixed in
1.10-rc1. Only the node classification still does not work. Also, I still
need to create /etc/puppet manually and place foreman.yaml in there because
node.rb is hardcoded to search for /etc/puppet/foreman.yaml

I managed to compile the latest build from source. Configured PuppetDB and
foreman reports. Funny thing is that although the setup is correct, the
reports are not getting populated on pgsql. No indication of POST
"/api/reports" with 201 from the logs. The database is practically empty
minus the configurations.

This is my first time digging deep into foreman so you might have to bear
with me a bit :slight_smile:

Any pointer will help.

··· On Thursday, June 11, 2015 at 7:58:15 PM UTC+5:30, Daniel Lobato wrote: > > On 06/11, Choon Ming Goh wrote: > > Hey all, > > > > Are there any timelines or milestones to puppet 4 support on foreman > yet? > > I'm using puppet 4 right now and having to deploy foreman on top of it > will > > be sweet. I've tried installing the packages manually and configure it > but > > it all fails on the rake commands. > > We're following Puppet 4 support on this tracker > http://projects.theforeman.org/issues/8447 > > For the moment it's not supported, but if you make it work it'd be great > to hear from you and get any patches you had to apply :) > > > > OS: Debian 7 > > Puppetserver: 2.1 (installed via apt) > > Foreman: 1.8 (installed via apt: foreman, foreman-postgresql) > > PuppetDB: 2.3.5 > > > > I've symlinked all the binaries from /opt/puppetlabs/bin to /usr/bin > hoping > > it'll help but I get the error below when trying to setup the database > > > > ~ # foreman-rake --trace db:migrate > > rake aborted! > > LoadError: cannot load such file -- facter > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > > > `require' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > > > `block in require' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in > > > `load_dependency' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:251:in > > > `require' > > /usr/share/foreman/lib/tasks/reset_permissions.rake:1:in ` (required)>' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in > > > `load' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in > > > `block in load' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:236:in > > > `load_dependency' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/activesupport-3.2.21/lib/active_support/dependencies.rb:245:in > > > `load' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:in > > > `block in load_tasks' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:in > > > `each' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/engine.rb:425:in > > > `load_tasks' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/application.rb:145:in > > > `load_tasks' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/railties-3.2.21/lib/rails/railtie/configurable.rb:30:in > > > `method_missing' > > /usr/share/foreman/Rakefile:7:in `' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in > > > `load' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/rake_module.rb:28:in > > > `load_rakefile' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:689:in > > > `raw_load_rakefile' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:94:in > > > `block in load_rakefile' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:176:in > > > `standard_exception_handling' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:93:in > > > `load_rakefile' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:77:in > > > `block in run' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:176:in > > > `standard_exception_handling' > > > /usr/share/foreman/vendor/ruby/1.9.1/gems/rake-10.4.2/lib/rake/application.rb:75:in > > > `run' > > /usr/bin/rake:27:in `' > > > > Hope someone can point me out to the right direction. I'm willing to > build > > from the nightly as well. > > > > > > > > -- > > 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 >

Ok, managed to get it to work. There are a few workarounds to get the
report + facts working on Puppet 4 and foreman:

  1. foreman.yaml is configured in /etc/puppetlabs/puppet
  2. node.rb for ENC is configured in /etc/puppetlabs/puppet
  3. foreman.rb for reporting is placed in
    /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports

foreman.yaml

puppetdir: /opt/puppetlabs/server/data/puppetserver

/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb

26: $settings_file = "/etc/puppetlabs/puppet/foreman.yaml"

/etc/puppetlabs/

dasboard

Settings -> Auth -> trusted_puppetmaster_hosts = [ puppet.example.com ]

This will get data into your setup with hosts details/facts/reports.

The next issue I'm facing is that there isn't any import button that I can
press on the Configure -> Puppet Classes page. Perhaps its removed from
1.9? Anyone can shed a light here? I would love to test the ENC
functionality.

This is my current setup for foreman 1.10-rc1 stable. Build from source on
centos 6.6 with puppetserver 2 and puppet version 4.2 installed. Everything
is working fine except for the ENC on puppet.

[root@foreman puppet]# ./node.rb foreman.olindata.vm

··· --- classes: ntp: parameters: puppetmaster: foreman.olindata.vm domainname: '' root_pw: foreman_env: production owner_name: Admin User owner_email: root@olindata.vm foreman_subnets: [] foreman_interfaces: - mac: 08:00:27:c2:5c:8d ip: 10.0.2.15 type: Interface name: foreman.olindata.vm attrs: network: 10.0.2.0 netmask: 255.255.255.0 mtu: 1500 virtual: false link: true identifier: eth0 managed: true primary: true provision: true subnet: - mac: 08:00:27:e8:14:f8 ip: 192.168.56.100 type: Interface name: '' attrs: network: 192.168.56.0 netmask: 255.255.255.0 mtu: 1500 virtual: false link: true identifier: eth1 managed: false primary: false provision: false subnet: environment: production [root@foreman puppet]# echo $? 0

[root@foreman ~]# puppet agent -t
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Find
/puppet/v3/node/foreman.olindata.vm?environment=production&configured_environment=production&tran…
resulted in 404 with the message: Not Found: Could not find node
foreman.olindata.vm
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Could not find node ‘foreman.olindata.vm’; cannot compile
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
[root@foreman ~]#

192.168.56.100 - - - 26/Oct/2015:01:06:36 -0400 “GET
/puppet/v3/node/foreman.olindata.vm?environment=production&configured_environment=production&transaction_uuid=b34c7f3d-675f-441f-8859-22e7a268a267&fail_on_404=true
HTTP/1.1” 404 50 192.168.56.100 192.168.56.100 8140 1654
192.168.56.100 - - - 26/Oct/2015:01:06:37 -0400 “GET
/puppet/v3/file_metadatas/pluginfacts?environment=production&links=follow&recurse=true&source_permissions=use&ignore=.svn&ignore=CVS&ignore=.git&checksum_type=md5
HTTP/1.1” 200 242 192.168.56.100 192.168.56.100 8140 615
192.168.56.100 - - - 26/Oct/2015:01:06:39 -0400 “GET
/puppet/v3/file_metadatas/plugins?environment=production&links=follow&recurse=true&source_permissions=ignore&ignore=.svn&ignore=CVS&ignore=.git&checksum_type=md5
HTTP/1.1” 200 53411 192.168.56.100 192.168.56.100 8140 1386
192.168.56.100 - - - 26/Oct/2015:01:06:44 -0400 “POST
/puppet/v3/catalog/foreman.olindata.vm HTTP/1.1” 400 57 192.168.56.100
192.168.56.100 8140 3151
192.168.56.100 - - - 26/Oct/2015:01:06:45 -0400 “PUT
/puppet/v3/report/foreman.olindata.vm?environment=production& HTTP/1.1” 200
30 192.168.56.100 192.168.56.100 8140 1583

There is nothing showing on the logs for the smart proxy nor foreman.

Maybe one of the devs or someone here can help me to iron out the issue?

OK. Found out I needed the smart proxy in order to import the classes. Is
there anyway to import the classes without using the smart proxy itself?
I've built the smart proxy from scratch but I'm facing an error where it
cannot send requests to puppet API

curl --cert /etc/puppetlabs/puppet/ssl/certs/puppet.example.com.pem --key /
etc/puppetlabs/puppet/ssl/private_keys/puppet.example.com.pem --cacert /etc/
puppetlabs/puppet/ssl/ca/ca_crt.pem -H 'Accept: pson' https:
//puppet.example.com:8443/puppet/v3/environments

puppet.example.com - - [12/Jun/2015:19:09:22 MYT] "GET
/puppet/v3/environments HTTP/1.1" 404 618

  • -> /puppet/v3/environments

The smart proxy is working for sure.

curl --cert /etc/puppetlabs/puppet/ssl/certs/puppet.example.com.pem --key /
etc/puppetlabs/puppet/ssl/private_keys/puppet.example.com.pem --cacert /etc/
puppetlabs/puppet/ssl/ca/ca_crt.pem -H 'Accept: pson' https:
//puppet.example.com:8443/features

["puppet"]
root@puppet:~

puppet.example.com - - [12/Jun/2015:19:03:23 MYT] "GET /features HTTP/1.1"
200 10

  • -> /features

Any guidance from the experts?

> This is my current setup for foreman 1.10-rc1 stable. Build from source
> on centos 6.6 with puppetserver 2 and puppet version 4.2 installed.
> Everything is working fine except for the ENC on puppet.
>
> >
[…]
> [root@foreman ~]# puppet agent -t
> Warning: Unable to fetch my node definition, but the agent run will
> continue:
> Warning: Find
> /puppet/v3/node/foreman.olindata.vm?environment=production&configured_environment=production&tran…
> resulted in 404 with the message: Not Found: Could not find node
> foreman.olindata.vm
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Could not find node 'foreman.olindata.vm'; cannot compile
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run

It's unclear whether the ENC is actually being executed by the Puppet
master. The messages you're seeing on the client don't say anything
about node.rb having failed.

Try adding some logging to it to determine if it is, and if not, verify
that the master configuration (external_nodes/node_terminus) is set
correctly and is active.

··· On 26/10/15 05:11, Choon Ming Goh wrote:


Dominic Cleal
dominic@cleal.org

Did you make any progress? I am implementing a similar setup, early in the
setup steps but would be interested to share insights.

··· On Friday, June 12, 2015 at 12:13:45 PM UTC+1, Choon Ming Goh wrote: > > OK. Found out I needed the smart proxy in order to import the classes. Is > there anyway to import the classes without using the smart proxy itself? > I've built the smart proxy from scratch but I'm facing an error where it > cannot send requests to puppet API > > curl --cert /etc/puppetlabs/puppet/ssl/certs/puppet.example.com.pem --key > /etc/puppetlabs/puppet/ssl/private_keys/puppet.example.com.pem --cacert / > etc/puppetlabs/puppet/ssl/ca/ca_crt.pem -H 'Accept: pson' https:// > puppet.example.com:8443/puppet/v3/environments > > puppet.example.com - - [12/Jun/2015:19:09:22 MYT] "GET > /puppet/v3/environments HTTP/1.1" 404 618 > - -> /puppet/v3/environments > > The smart proxy is working for sure. > > curl --cert /etc/puppetlabs/puppet/ssl/certs/puppet.example.com.pem --key > /etc/puppetlabs/puppet/ssl/private_keys/puppet.example.com.pem --cacert / > etc/puppetlabs/puppet/ssl/ca/ca_crt.pem -H 'Accept: pson' https:// > puppet.example.com:8443/features > > ["puppet"] > root@puppet:~ > > puppet.example.com - - [12/Jun/2015:19:03:23 MYT] "GET /features HTTP/1.1" > 200 10 > - -> /features > > Any guidance from the experts? >

I did not. I paused my work because I was engaged with another project. The version 1.9 has been released and I have yet to test on it.

··· -- Choon Ming

On August 28, 2015 at 2:41:19 PM, KEIGNAERT Mathieu (mathieu.keignaert@gmail.com) wrote:

Did you make any progress? I am implementing a similar setup, early in the setup steps but would be interested to share insights.

On Friday, June 12, 2015 at 12:13:45 PM UTC+1, Choon Ming Goh wrote:
OK. Found out I needed the smart proxy in order to import the classes. Is there anyway to import the classes without using the smart proxy itself? I’ve built the smart proxy from scratch but I’m facing an error where it cannot send requests to puppet API

curl --cert /etc/puppetlabs/puppet/ssl/certs/puppet.example.com.pem --key /etc/puppetlabs/puppet/ssl/private_keys/puppet.example.com.pem --cacert /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem -H ‘Accept: pson’ https://puppet.example.com:8443/puppet/v3/environments

puppet.example.com - - [12/Jun/2015:19:09:22 MYT] “GET /puppet/v3/environments HTTP/1.1” 404 618

  • -> /puppet/v3/environments

The smart proxy is working for sure.

curl --cert /etc/puppetlabs/puppet/ssl/certs/puppet.example.com.pem --key /etc/puppetlabs/puppet/ssl/private_keys/puppet.example.com.pem --cacert /etc/puppetlabs/puppet/ssl/ca/ca_crt.pem -H ‘Accept: pson’ https://puppet.example.com:8443/features

[“puppet”]
root@puppet:~

puppet.example.com - - [12/Jun/2015:19:03:23 MYT] “GET /features HTTP/1.1” 200 10

  • -> /features

Any guidance from the experts?

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/HOT9RSSmAMU/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 http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.