Provisioning setup Pre-requisites

Support
1

Hello,

I try to start with provisioning, but I fail at the very beginning.

When I click to Provisioning setup I see the following message:

No network interfaces listed in $interfaces fact
Not available until pre-requisites satisified.

I don't get it. Why and where is there a interfaces fact missing? The smart
proxy got a network interface configured.
Unfortunately, I wasn't able to find anything what explain my problem.

Thanks
Björn

2

It's looking for a host in Foreman's DB for the Foreman server itself,
then checking the facts uploaded by Puppet.

Check in the host list that you have the Foreman server itself listed,
then click it, then Facts, and see if "interfaces" is listed. What
value does it have?

Try running "facter interfaces" too on the server to see its output.

··· On 15/09/14 09:43, Björn wrote: > Hello, > > I try to start with provisioning, but I fail at the very beginning. > > When I click to Provisioning setup I see the following message: > > No network interfaces listed in $interfaces fact > > > Not available until pre-requisites satisified. > > I don't get it. Why and where is there a interfaces fact missing? The > smart proxy got a network interface configured. > Unfortunately, I wasn't able to find anything what explain my problem.

–
Dominic Cleal
Red Hat Engineering

3

The output of "facter interfaces" is fine:

#facter interfaces
#eth0,lo

The database table fact_names is empty…

When I run a puppet agent on one node I see this in apache log:

puppet - - [15/Sep/2014:16:17:27 +0200] "GET /node/client01?format=yml
HTTP/1.1" 200 769 "-" "-"
puppet - - [15/Sep/2014:16:17:30 +0200] "POST /api/hosts/facts HTTP/1.1"
422 72 "-" "-"
puppet - - [15/Sep/2014:16:17:30 +0200] "GET /node/client01?format=yml
HTTP/1.1" 200 769 "-" "-"

I guess puppet try to insert the facts with the POST Request and that
failed, isn't it?

#cat /etc/puppet/foreman.yaml

··· --- :url: "https://puppet" :ssl_ca: "/var/lib/puppet/ssl/certs/ca.pem" :ssl_cert: "/var/lib/puppet/ssl/certs/puppet.pem" :ssl_key: "/var/lib/puppet/ssl/private_keys/puppet.pem" :user: "" :password: "" :puppetdir: "/var/lib/puppet" :puppetuser: "puppet" :facts: true :timeout: 10 :threads: null

Regards,
Björn

Am Montag, 15. September 2014 14:42:55 UTC+2 schrieb Dominic Cleal:

On 15/09/14 09:43, Björn wrote:

Hello,

I try to start with provisioning, but I fail at the very beginning.

When I click to Provisioning setup I see the following message:

No network interfaces listed in $interfaces fact

Not available until pre-requisites satisified.

I don’t get it. Why and where is there a interfaces fact missing? The
smart proxy got a network interface configured.
Unfortunately, I wasn’t able to find anything what explain my problem.

It’s looking for a host in Foreman’s DB for the Foreman server itself,
then checking the facts uploaded by Puppet.

Check in the host list that you have the Foreman server itself listed,
then click it, then Facts, and see if “interfaces” is listed. What
value does it have?

Try running “facter interfaces” too on the server to see its output.

–
Dominic Cleal
Red Hat Engineering

4

Yeah, that's right. Check /var/log/foreman/production.log when running
"puppet agent -t" and it may log a reason.

··· On 15/09/14 15:26, Björn wrote: > puppet - - [15/Sep/2014:16:17:30 +0200] "POST /api/hosts/facts HTTP/1.1" > 422 72 "-" "-" > puppet - - [15/Sep/2014:16:17:30 +0200] "GET /node/client01?format=yml > HTTP/1.1" 200 769 "-" "-" > > I guess puppet try to insert the facts with the POST Request and that > failed, isn't it?

–
Dominic Cleal
Red Hat Engineering

5

>
> > puppet - - [15/Sep/2014:16:17:30 +0200] "POST /api/hosts/facts HTTP/1.1"
> > 422 72 "-" "-"
> > puppet - - [15/Sep/2014:16:17:30 +0200] "GET /node/client01?format=yml
> > HTTP/1.1" 200 769 "-" "-"
> >
> > I guess puppet try to insert the facts with the POST Request and that
> > failed, isn't it?
>
> Yeah, that's right. Check /var/log/foreman/production.log when running
> "puppet agent -t" and it may log a reason.
>

I run "foreman-installer --foreman-proxy-register-in-foreman=false", but
nothing changed.

This is the output in /var/log/foreman/production.log:

Started GET "/node/client.domain.de?format=yml" for ip-address at
2014-09-16 09:26:40 +0200
Processing by HostsController#externalNodes as YML
Parameters: {"name"=>"client.domain.de"}
Rendered text template (0.0ms)
Completed 200 OK in 51ms (Views: 0.6ms | ActiveRecord: 2.0ms)

Started POST "/api/hosts/facts" for ip-address at 2014-09-16 09:26:43 +0200
Processing by Api::V2::HostsController#facts as JSON
Parameters: {"certname"=>"client.domain.de", "facts"=>"[FILTERED]",
"name"=>"CLIENT.domain.de", "apiv"=>"v2",
:host=>{"name"=>"CLIENT.domain.de", "certname"=>"client.domain.de"}}
Completed 422 Unprocessable Entity in 7ms (Views: 0.2ms | ActiveRecord:
0.3ms)

Started GET "/node/client.domain.de?format=yml" for ip-address at
2014-09-16 09:26:43 +0200
Processing by HostsController#externalNodes as YML
Parameters: {"name"=>"client.domain.de"}
Rendered text template (0.0ms)
Completed 200 OK in 144ms (Views: 0.6ms | ActiveRecord: 1.7ms)

Started POST "/api/reports" for ip-address at 2014-09-16 09:27:24 +0200
Processing by Api::V2::ReportsController#create as JSON
Parameters: {"report"=>"[FILTERED]", "apiv"=>"v2"}
processing report for client.domain.de
Imported report for client.domain.de in 0.05 seconds
Completed 201 Created in 55ms (Views: 3.6ms | ActiveRecord: 0.0ms)
Connecting to database specified by database.yml
Connecting to database specified by database.yml

··· Am Montag, 15. September 2014 16:28:23 UTC+2 schrieb Dominic Cleal: > On 15/09/14 15:26, Björn wrote:

–
Dominic Cleal
Red Hat Engineering