Foreman-installer --scenario katello SUCCESS BUT cannot register the server it was run on

foreman newbie here.
I have ( multiple times! ) successfully run
foreman-installer --scenario katello
foreman 1.13.2
katello 3.2.0

I can then run
puppet agent --test
which outputs:
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for seainfspwk400.concurasp.com
Info: Applying configuration version '1482251162'

But the server does not appear as a host in foreman ( it DOES show up as a
proxy )

Not sure where to go next to fix this!

Hello Chris,

I am a foreman newbie myself but did you register katello as a content host
yet?
rpm -ivh https://<katello host>/pub/katello-ca-consumer-<your katello host
and version>.noarch.rpm
subscription-manager register [–org=<your-org> --activationkey=<your ak>]
?

Pascal

··· On Wednesday, December 21, 2016 at 10:15:03 AM UTC+1, Chris Bone wrote: > > foreman newbie here. > I have ( multiple times! ) successfully run > foreman-installer --scenario katello > foreman 1.13.2 > katello 3.2.0 > > I can then run > puppet agent --test > which outputs: > Info: Retrieving pluginfacts > Info: Retrieving plugin > Info: Caching catalog for seainfspwk400.concurasp.com > Info: Applying configuration version '1482251162' > > But the server does not appear as a host in foreman ( it DOES show up as a > proxy ) > > Not sure where to go next to fix this! >

> From: "Chris Bone" <bone.chris@gmail.com>
> To: "Foreman users" <foreman-users@googlegroups.com>
> Sent: Tuesday, December 20, 2016 11:27:32 AM
> Subject: [foreman-users] foreman-installer --scenario katello SUCCESS BUT cannot register the server it was run
> on
>
> foreman newbie here.
> I have ( multiple times! ) successfully run
> foreman-installer --scenario katello
> foreman 1.13.2
> katello 3.2.0
>
> I can then run
> puppet agent --test
> which outputs:
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Caching catalog for seainfspwk400.concurasp.com
> Info: Applying configuration version '1482251162'
>
> But the server does not appear as a host in foreman ( it DOES show up as a
> proxy )
>
> Not sure where to go next to fix this!

In your case, it's most likely being hidden by your Organization selector
in the upper left corner. We don't have any way to know what organization
or location to put Puppet-reported hosts in so they are created without one.

Change to any org/any loc and you'll probably see it.

··· ----- Original Message -----


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

> Hello Chris,
>
> I am a foreman newbie myself but did you register katello as a content
> host yet?
> rpm -ivh https://<katello host>/pub/katello-ca-consumer-<your katello
> host and version>.noarch.rpm
> subscription-manager register [–org=<your-org> --activationkey=<your ak>]
> ?
>
> Pascal
>

another option (or additionally) is to run puppet on your foreman host,
simply by puppet agent -t --server hostname -f will most likely register
it as well.

Ohad

··· On Wed, Dec 21, 2016 at 11:35 AM, pascalp wrote:

On Wednesday, December 21, 2016 at 10:15:03 AM UTC+1, Chris Bone wrote:

foreman newbie here.
I have ( multiple times! ) successfully run
foreman-installer --scenario katello
foreman 1.13.2
katello 3.2.0

I can then run
puppet agent --test
which outputs:
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for seainfspwk400.concurasp.com
Info: Applying configuration version ‘1482251162’

But the server does not appear as a host in foreman ( it DOES show up as
a proxy )

Not sure where to go next to fix this!


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

Is the right answer! Boy do I feel foolish.
Thanks.

··· On Wednesday, December 21, 2016 at 8:41:14 AM UTC-6, stephen wrote: > > > > ----- Original Message ----- > > From: "Chris Bone" <bone....@gmail.com > > > To: "Foreman users" <forema...@googlegroups.com > > > Sent: Tuesday, December 20, 2016 11:27:32 AM > > Subject: [foreman-users] foreman-installer --scenario katello > SUCCESS BUT cannot register the server it was run > > on > > > > foreman newbie here. > > I have ( multiple times! ) successfully run > > foreman-installer --scenario katello > > foreman 1.13.2 > > katello 3.2.0 > > > > I can then run > > puppet agent --test > > which outputs: > > Info: Retrieving pluginfacts > > Info: Retrieving plugin > > Info: Caching catalog for seainfspwk400.concurasp.com > > Info: Applying configuration version '1482251162' > > > > But the server does not appear as a host in foreman ( it DOES show up as > a > > proxy ) > > > > Not sure where to go next to fix this! > > In your case, it's most likely being hidden by your Organization selector > in the upper left corner. We don't have any way to know what organization > or location to put Puppet-reported hosts in so they are created without > one. > > Change to any org/any loc and you'll probably see it. > > > > > > -- > > 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 https://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/d/optout. > > >

Something might be going wrong with this latest release. I'm testing the
latest Katello/Foreman release too and the server does not manage to
register to itself.

Running the puppet command suggested above gives:

root@katello ~]# puppet agent -t --server hostname -f
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 500 on SERVER: Server Error: Failed to find
katello.innes.net via exec: Execution of '/etc/puppetlabs/puppet/node.rb
katello.innes.net' returned 1:
Info: Retrieving pluginfacts
Info: Retrieving plugin
Error: Could not retrieve catalog from remote server: Error 500 on SERVER:
Server Error: Failed when searching for node katello.innes.net: Failed to
find katello.innes.net via exec: Execution of
'/etc/puppetlabs/puppet/node.rb katello.innes.net' returned 1:
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run
[root@katello ~]#

This is a Puppet 4 build I've installed.

Also seeing the following in
/var/log/puppetlabs/puppetserver/puppetserver.log when I run the puppet
agent command:

2016-12-21 12:47:40,724 WARN [qtp1406891402-75] [c.p.p.ShellUtils]
Executed an external process which logged to STDERR: Could not send facts
to Foreman: Permission denied - /etc/puppetlabs/puppet/ssl/client_key.pem

2016-12-21 12:47:40,726 ERROR [qtp1406891402-75] [puppetserver] Puppet
Server Error: Failed to find katello.innes.net via exec: Execution of
'/etc/puppetlabs/puppet/node.rb katello.innes.net' returned 1:
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:44:in
execute&#39; file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:14:ininitialize_execution_stub'
org/jruby/RubyProc.java:281:in call&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:194:inexecute'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:33:in
execute&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/exec.rb:19:infind'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:17:in
find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:infind'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:in
do_find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:incall'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in
override&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:inoverride'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
call&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:inprocess'
org/jruby/RubyArray.java:1613:in each&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:inprofile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
profile&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:inprocess'
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
handleRequest&#39; Puppet$$Server$$Master_505362540.gen:13:inhandleRequest'
request_handler_core.clj:273:in invoke&#39; jruby_request.clj:46:ininvoke'
jruby_request.clj:31:in invoke&#39; request_handler_service.clj:34:inhandle_request'
request_handler.clj:3:in invoke&#39; request_handler.clj:3:ininvoke'
core.clj:2515:in invoke&#39; ring_middleware.clj:284:ininvoke'
core.clj:168:in invoke&#39; core.clj:211:ininvoke'
core.clj:45:in invoke&#39; core.clj:343:ininvoke'
core.clj:51:in invoke&#39; ringutils.clj:83:ininvoke'
master_core.clj:411:in invoke&#39; ring.clj:21:ininvoke'
ring.clj:12:in invoke&#39; comidi.clj:249:ininvoke'
jetty9_core.clj:424:in invoke&#39; normalized_uri_helpers.clj:80:ininvoke'
2016-12-21 12:47:41,309 WARN [qtp1406891402-73] [c.p.p.ShellUtils]
Executed an external process which logged to STDERR: Could not send facts
to Foreman: Permission denied - /etc/puppetlabs/puppet/ssl/client_key.pem

2016-12-21 12:47:41,317 ERROR [qtp1406891402-73] [puppetserver] Puppet
Failed when searching for node katello.innes.net: Failed to find
katello.innes.net via exec: Execution of '/etc/puppetlabs/puppet/node.rb
katello.innes.net' returned 1:
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:44:in
execute&#39; file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:14:ininitialize_execution_stub'
org/jruby/RubyProc.java:281:in call&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:194:inexecute'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:33:in
execute&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/exec.rb:19:infind'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:17:in
find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:infind'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:295:in
find_node&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:inprofile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
profile&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:292:infind_node'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:332:in
node_from_request&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:50:infind'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in
find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:indo_find'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:in
call&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:inoverride'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in override&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:incall'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:in
process&#39; org/jruby/RubyArray.java:1613:ineach'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
profile&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:inprofile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:in
process&#39; file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:inhandleRequest'
Puppet$$Server$$Master_505362540.gen:13:in handleRequest&#39; request_handler_core.clj:273:ininvoke'
jruby_request.clj:46:in invoke&#39; jruby_request.clj:31:ininvoke'
request_handler_service.clj:34:in handle_request&#39; request_handler.clj:3:ininvoke'
request_handler.clj:3:in invoke&#39; core.clj:2515:ininvoke'
ring_middleware.clj:284:in invoke&#39; core.clj:168:ininvoke'
core.clj:211:in invoke&#39; core.clj:45:ininvoke'
core.clj:343:in invoke&#39; core.clj:51:ininvoke'
ringutils.clj:83:in invoke&#39; master_core.clj:428:ininvoke'
ring.clj:21:in invoke&#39; ring.clj:12:ininvoke'
comidi.clj:249:in invoke&#39; jetty9_core.clj:424:ininvoke'
normalized_uri_helpers.clj:80:in invoke&#39; 2016-12-21 12:47:41,317 ERROR [qtp1406891402-73] [puppetserver] Puppet Server Error: Failed when searching for node katello.innes.net: Failed to find katello.innes.net via exec: Execution of &#39;/etc/puppetlabs/puppet/node.rb katello.innes.net&#39; returned 1: file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:44:inexecute'
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/execution.rb:14:in
initialize_execution_stub&#39; org/jruby/RubyProc.java:281:incall'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/execution.rb:194:in
execute&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:33:inexecute'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/exec.rb:19:in
find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/node/exec.rb:17:infind'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:in
find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:295:infind_node'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:in
profile&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:inprofile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:292:in
find_node&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:332:innode_from_request'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/catalog/compiler.rb:50:in
find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:194:infind'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:121:in
do_find&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:incall'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in
override&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:inoverride'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
call&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:inprocess'
org/jruby/RubyArray.java:1613:in each&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:inprofile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
profile&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:inprocess'
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
handleRequest&#39; Puppet$$Server$$Master_505362540.gen:13:inhandleRequest'
request_handler_core.clj:273:in invoke&#39; jruby_request.clj:46:ininvoke'
jruby_request.clj:31:in invoke&#39; request_handler_service.clj:34:inhandle_request'
request_handler.clj:3:in invoke&#39; request_handler.clj:3:ininvoke'
core.clj:2515:in invoke&#39; ring_middleware.clj:284:ininvoke'
core.clj:168:in invoke&#39; core.clj:211:ininvoke'
core.clj:45:in invoke&#39; core.clj:343:ininvoke'
core.clj:51:in invoke&#39; ringutils.clj:83:ininvoke'
master_core.clj:428:in invoke&#39; ring.clj:21:ininvoke'
ring.clj:12:in invoke&#39; comidi.clj:249:ininvoke'
jetty9_core.clj:424:in invoke&#39; normalized_uri_helpers.clj:80:ininvoke'
2016-12-21 12:47:41,355 ERROR [qtp1406891402-76] [puppetserver] Puppet
Report processor failed: Could not send report to Foreman at
https://katello.innes.net/api/config_reports: Permission denied -
/etc/puppetlabs/puppet/ssl/client_key.pem
["org/jruby/RubyIO.java:3804:in read&#39;&quot;, &quot;org/jruby/RubyIO.java:3987:inread'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb:58:in
process&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:37:inprocess'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:53:in
processors&#39;&quot;, &quot;org/jruby/RubyArray.java:1613:ineach'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:51:in
processors&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:30:inprocess'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:14:in
save&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:285:insave'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:176:in
do_save&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:incall'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in
override&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:inoverride'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
call&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:inprocess'", "org/jruby/RubyArray.java:1613:in each&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:inprocess'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
process&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:inprocess'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
process&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:inprofile'",
"/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
profile&#39;&quot;, &quot;/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:inprocess'",
"file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
handleRequest&#39;&quot;, &quot;Puppet$$Server$$Master_505362540.gen:13:inhandleRequest'", "request_handler_core.clj:273:in invoke&#39;&quot;, &quot;jruby_request.clj:46:ininvoke'", "jruby_request.clj:31:in invoke&#39;&quot;, &quot;request_handler_service.clj:34:inhandle_request'",
"request_handler.clj:3:in invoke&#39;&quot;, &quot;request_handler.clj:3:ininvoke'",
"core.clj:2515:in invoke&#39;&quot;, &quot;ring_middleware.clj:284:ininvoke'",
"core.clj:168:in invoke&#39;&quot;, &quot;core.clj:211:ininvoke'", "core.clj:45:in
invoke&#39;&quot;, &quot;core.clj:343:ininvoke'", "core.clj:51:in invoke&#39;&quot;, &quot;ringutils.clj:83:ininvoke'", "master_core.clj:430:in invoke&#39;&quot;, &quot;ring.clj:21:ininvoke'", "ring.clj:12:in invoke&#39;&quot;, &quot;comidi.clj:249:ininvoke'", "jetty9_core.clj:424:in invoke&#39;&quot;, &quot;normalized_uri_helpers.clj:80:ininvoke'"]
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/reports/foreman.rb:67:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:37:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:53:in
processors&#39; org/jruby/RubyArray.java:1613:ineach'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:51:in
processors&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:30:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/report/processor.rb:14:in
save&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:285:insave'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:176:in
do_save&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:48:incall'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in
override&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:inoverride'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/api/indirected_routes.rb:47:in
call&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:82:inprocess'
org/jruby/RubyArray.java:1613:in each&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:81:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/route.rb:87:inprocess'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:60:in
process&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler/around_profiler.rb:58:inprofile'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/profiler.rb:51:in
profile&#39; /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/network/http/handler.rb:58:inprocess'
file:/opt/puppetlabs/server/apps/puppetserver/puppet-server-release.jar!/puppetserver-lib/puppet/server/master.rb:42:in
handleRequest&#39; Puppet$$Server$$Master_505362540.gen:13:inhandleRequest'
request_handler_core.clj:273:in invoke&#39; jruby_request.clj:46:ininvoke'
jruby_request.clj:31:in invoke&#39; request_handler_service.clj:34:inhandle_request'
request_handler.clj:3:in invoke&#39; request_handler.clj:3:ininvoke'
core.clj:2515:in invoke&#39; ring_middleware.clj:284:ininvoke'
core.clj:168:in invoke&#39; core.clj:211:ininvoke'
core.clj:45:in invoke&#39; core.clj:343:ininvoke'
core.clj:51:in invoke&#39; ringutils.clj:83:ininvoke'
master_core.clj:430:in invoke&#39; ring.clj:21:ininvoke'
ring.clj:12:in invoke&#39; comidi.clj:249:ininvoke'
jetty9_core.clj:424:in invoke&#39; normalized_uri_helpers.clj:80:ininvoke'

··· On Wednesday, 21 December 2016 12:45:34 UTC, Duncan Innes wrote: > > Something might be going wrong with this latest release. I'm testing the > latest Katello/Foreman release too and the server does not manage to > register to itself. > > Running the puppet command suggested above gives: > > root@katello ~]# puppet agent -t --server `hostname -f` > Warning: Unable to fetch my node definition, but the agent run will > continue: > Warning: Error 500 on SERVER: Server Error: Failed to find > katello.innes.net via exec: Execution of '/etc/puppetlabs/puppet/node.rb > katello.innes.net' returned 1: > Info: Retrieving pluginfacts > Info: Retrieving plugin > Error: Could not retrieve catalog from remote server: Error 500 on SERVER: > Server Error: Failed when searching for node katello.innes.net: Failed to > find katello.innes.net via exec: Execution of > '/etc/puppetlabs/puppet/node.rb katello.innes.net' returned 1: > Warning: Not using cache on failed catalog > Error: Could not retrieve catalog; skipping run > [root@katello ~]# > > This is a Puppet 4 build I've installed. >

Ignore this. A new clea build with the latest Foreman release shows no
sign of this error. Host appears as expected. Sorry for noise.

D

··· On Wednesday, 21 December 2016 12:52:40 UTC, Duncan Innes wrote: > > > > Also seeing the following in > /var/log/puppetlabs/puppetserver/puppetserver.log when I run the puppet > agent command: > > 2016-12-21 12:47:40,724 WARN [qtp1406891402-75] [c.p.p.ShellUtils] > Executed an external process which logged to STDERR: Could not send facts > to Foreman: Permission denied - /etc/puppetlabs/puppet/ssl/client_key.pem > >

> From: "Chris Bone" <bone.chris@gmail.com>
> To: "Foreman users" <foreman-users@googlegroups.com>
> Cc: stephen@redhat.com
> Sent: Wednesday, December 21, 2016 3:57:24 PM
> Subject: Re: [foreman-users] foreman-installer --scenario katello SUCCESS BUT cannot register the server it was
> run on
>
> Is the right answer! Boy do I feel foolish.

Lol, don't, org/locs aren't a good user experience. Unless someone
tells you about that org/location selector, it's hard to discover
where those hosts go.

··· ----- Original Message -----

Thanks.

On Wednesday, December 21, 2016 at 8:41:14 AM UTC-6, stephen wrote:

----- Original Message -----

From: “Chris Bone” <bone....@gmail.com <javascript:>>
To: “Foreman users” <forema...@googlegroups.com <javascript:>>
Sent: Tuesday, December 20, 2016 11:27:32 AM
Subject: [foreman-users] foreman-installer --scenario katello
SUCCESS BUT cannot register the server it was run
on

foreman newbie here.
I have ( multiple times! ) successfully run
foreman-installer --scenario katello
foreman 1.13.2
katello 3.2.0

I can then run
puppet agent --test
which outputs:
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for seainfspwk400.concurasp.com
Info: Applying configuration version ‘1482251162’

But the server does not appear as a host in foreman ( it DOES show up as
a
proxy )

Not sure where to go next to fix this!

In your case, it’s most likely being hidden by your Organization selector
in the upper left corner. We don’t have any way to know what organization
or location to put Puppet-reported hosts in so they are created without
one.

Change to any org/any loc and you’ll probably see it.


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 <javascript:>.
To post to this group, send email to forema...@googlegroups.com
<javascript:>.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


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

>
>
> >
> > Is the right answer! Boy do I feel foolish.
>
> Lol, don't, org/locs aren't a good user experience. Unless someone
> tells you about that org/location selector, it's hard to discover
> where those hosts go.
>
>
What gets me is the apparent lack of an attempt at logic. If there is only
1 Org created, it might not be the worst logic to register against that Org
rather than leaving it hanging. Or against the Org which was defined by
–foreman-initial-organization?

Not sure I would do the same for Loc as that seems a different question to
me.

Is it hard to figure out when the Katello server checks in for the first
time?