I've a setup with foreman-server & foreman-proxy running on 2 separate
servers.
Foreman-server sits behind firewall and has access to foreman-proxy on port
8443.
When I try to post discovery facts from new discovered hosts via
foreman-proxy, proxy is failing to report them to server since it looks for
port 443 on foreman-server (as defined in settings.yml)
I can see following in proxy.log every time there is instance of facts
reporting.
E, [2015-08-01T09:51:22.555547 #20272] ERROR – : failed to update Foreman:
Connection refused - connect(2)
I am trying to avoid to open any ports from proxy to foreman, since
foreman-server sits in restricted subnet.
Is there any way I can sync up these facts upto server without having to
open access from proxy to foreman?
And ensure Foreman is configured to use the proxy, by configuring the PXE template
to point to the proxy and having the foreman url set correctly: Foreman :: Plugin Manuals
···
----- Original Message -----
> From: "nitin sonawane"
> To: "Foreman users"
> Sent: Saturday, August 1, 2015 8:20:39 AM
> Subject: [foreman-users] Discovery facts reporting to foreman server
>
> Hey Guys,
>
> I've a setup with foreman-server & foreman-proxy running on 2 separate
> servers.
>
> Foreman-server sits behind firewall and has access to foreman-proxy on port
> 8443.
>
> When I try to post discovery facts from new discovered hosts via
> foreman-proxy, proxy is failing to report them to server since it looks for
> port 443 on foreman-server (as defined in settings.yml)
>
> I can see following in proxy.log every time there is instance of facts
> reporting.
>
> E, [2015-08-01T09:51:22.555547 #20272] ERROR -- : failed to update Foreman:
> Connection refused - connect(2)
>
> I am trying to avoid to open any ports from proxy to foreman, since
> foreman-server sits in restricted subnet.
>
> Is there any way I can sync up these facts upto server without having to
> open access from proxy to foreman?
>
> Thanks,
>
> Nitin
>
>
>
> --
> 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.
>
Discovery plugin is installed on the proxy as well as foreman server. The
problem is, discovered hosts report facts to foreman proxy but, proxy is
not able to upload those facts to server. Proxy seems to be trying to
connect to port 443 on foreman server to upload facts. Foreman server is in
a restricted subnet for us to open access.
I am looking for a way to have foreman server pull those facts from proxy
if that's possible.
Thanks Stephen,
Nitin
···
On Aug 1, 2015 8:41 AM, "Stephen Benjamin" wrote:
Have a look at installing the discovery plugin on your proxy:
From: “nitin sonawane” nitnrs@gmail.com
To: “Foreman users” foreman-users@googlegroups.com
Sent: Saturday, August 1, 2015 8:20:39 AM
Subject: [foreman-users] Discovery facts reporting to foreman server
Hey Guys,
I’ve a setup with foreman-server & foreman-proxy running on 2 separate
servers.
Foreman-server sits behind firewall and has access to foreman-proxy on
port
8443.
When I try to post discovery facts from new discovered hosts via
foreman-proxy, proxy is failing to report them to server since it looks
for
port 443 on foreman-server (as defined in settings.yml)
I can see following in proxy.log every time there is instance of facts
reporting.
E, [2015-08-01T09:51:22.555547 #20272] ERROR – : failed to update
Foreman:
Connection refused - connect(2)
I am trying to avoid to open any ports from proxy to foreman, since
foreman-server sits in restricted subnet.
Is there any way I can sync up these facts upto server without having to
open access from proxy to foreman?
> From: "nitin" <nitnrs@gmail.com>
> To: foreman-users@googlegroups.com
> Sent: Saturday, August 1, 2015 11:55:00 AM
> Subject: Re: [foreman-users] Discovery facts reporting to foreman server
>
> Discovery plugin is installed on the proxy as well as foreman server. The
> problem is, discovered hosts report facts to foreman proxy but, proxy is
> not able to upload those facts to server. Proxy seems to be trying to
> connect to port 443 on foreman server to upload facts. Foreman server is in
> a restricted subnet for us to open access.
>
> I am looking for a way to have foreman server pull those facts from proxy
> if that's possible.
Not currently, you could file a request, but generally we expect
the proxy to be able to talk to the Foreman and vice versa.
···
----- Original Message -----
Thanks Stephen,
Nitin
On Aug 1, 2015 8:41 AM, “Stephen Benjamin” stephen@redhat.com wrote:
Have a look at installing the discovery plugin on your proxy:
From: “nitin sonawane” nitnrs@gmail.com
To: “Foreman users” foreman-users@googlegroups.com
Sent: Saturday, August 1, 2015 8:20:39 AM
Subject: [foreman-users] Discovery facts reporting to foreman server
Hey Guys,
I’ve a setup with foreman-server & foreman-proxy running on 2 separate
servers.
Foreman-server sits behind firewall and has access to foreman-proxy on
port
8443.
When I try to post discovery facts from new discovered hosts via
foreman-proxy, proxy is failing to report them to server since it looks
for
port 443 on foreman-server (as defined in settings.yml)
I can see following in proxy.log every time there is instance of facts
reporting.
E, [2015-08-01T09:51:22.555547 #20272] ERROR – : failed to update
Foreman:
Connection refused - connect(2)
I am trying to avoid to open any ports from proxy to foreman, since
foreman-server sits in restricted subnet.
Is there any way I can sync up these facts upto server without having to
open access from proxy to foreman?
