Foreman Discovery 2.0: http://foreman.example.org/discovery/create is a 404?

Stefan_Lasiewski · January 29, 2015, 1:58am

Hi All,

I recently updated from Foreman Discovery 1.4 to Foreman Discovery 2.0,
following the instructions at
Foreman :: Plugin Manuals .

I was able to boot one host successfully and load facts to Foreman, but
then something happened and now the host cannot communicate with the
Foreman Proxy.

The host will load the fdi-image fine. When the image tries to register
itself, it hits the URL http://foreman.example.org/discovery/create but it
gets a 404 response.

When I look on my Foreman host at /var/log/httpd/foreman_access.log , I see
the following errors:

192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] "POST /discovery/create
HTTP/1.1" 404 431 "-" "Ruby"
192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] "POST /discovery/create
HTTP/1.1" 404 431 "-" "Ruby"
192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] "POST /discovery/create
HTTP/1.1" 404 431 "-" "Ruby"
192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] "POST /discovery/create
HTTP/1.1" 404 431 "-" "Ruby"

I am using the following APPEND line:

APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop root=live:/fdi.iso
rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0
rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset
proxy.url=http://foreman.example.org proxy.type=proxy

From what I see at

github.com

theforeman/foreman-discovery-image/blob/master/root/usr/bin/discovery-register

#!/usr/bin/env ruby
#
# vim: ts=2:sw=2:et
#
# Copyright (C) 2012-2014 Red Hat, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; version 2 of the License.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston,
# MA  02110-1301, USA.  A copy of the GNU General Public License is
# also available at http://www.gnu.org/copyleft/gpl.html.

This file has been truncated. show original

, if the proxy_type is set to 'proxy', then the FDI should contact
/discovery/create :

facts_url = if proxy_type == 'proxy'
"#{uri.path}/discovery/create"
else
"#{uri.path}/api/v2/discovered_hosts/facts"
end

It looks to me like Foreman is no longer serving /discovery/create? Any
idea why?

I'm uncertain if this behavior is a bug, or if I broke something. If it's a
bug, I can file a bug report.

Thanks for the help,

-= Stefan

lzap · January 29, 2015, 10:04am

> 192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] "POST /discovery/create
> HTTP/1.1" 404 431 "-" "Ruby"
> 192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] "POST /discovery/create
> HTTP/1.1" 404 431 "-" "Ruby"
> 192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] "POST /discovery/create
> HTTP/1.1" 404 431 "-" "Ruby"
> 192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] "POST /discovery/create
> HTTP/1.1" 404 431 "-" "Ruby"

Hello,

it looks like you configured image in Proxy mode against Foreman. Do you
plan to use smart-proxy for communication or not? It looks like not, in
that case set proxy.type=foreman and it should work. If you plan to use
proxy discovery plugin, change the proxy.url to your smart-proxy and
keep the "proxy" type.

We are still working on upgrade instructions.

···

-- Later, Lukas #lzap Zapletal

Stefan_Lasiewski · January 29, 2015, 7:27pm

Lukas,

Thanks for that explanation. I was intending to use the Proxy Discovery
plugin, which is why I set proxy.type=proxy and proxy.url= http://foreman.example.org, and I thought this worked at least once but I
may be wrong.

I figured out that never actually installed the Foreman Proxy Discovery
plugin. It doesn't exist in the Repository.
http://theforeman.org/plugins/foreman_discovery/2.0/#2.2ForemanProxyDiscoveryplugin
says

To install the plugin, do
>
> # yum install rubygem-smart_proxy_discovery
>
> on Fedora and Red Hat systems
>

However, there is no such file named 'rubygem-smart_proxy_discovery at
http://yum.theforeman.org/plugins/1.7/el6/x86_64/ .

-= Stefan

···

On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal wrote:

192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” “Ruby”

Hello,

it looks like you configured image in Proxy mode against Foreman. Do you
plan to use smart-proxy for communication or not? It looks like not, in
that case set proxy.type=foreman and it should work. If you plan to use
proxy discovery plugin, change the proxy.url to your smart-proxy and
keep the “proxy” type.

We are still working on upgrade instructions.

–
Later,
Lukas #lzap Zapletal

–
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/SJiBADLHJW8/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.

Stefan_Lasiewski · January 29, 2015, 7:28pm

I've started using proxy.type=foreman again and my nodes can register
facts again.

Thanks,

-= Stefan

···

On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski wrote:

Lukas,

Thanks for that explanation. I was intending to use the Proxy Discovery
plugin, which is why I set proxy.type=proxy and proxy.url= http://foreman.example.org, and I thought this worked at least once but
I may be wrong.

I figured out that never actually installed the Foreman Proxy Discovery
plugin. It doesn’t exist in the Repository.
Foreman :: Plugin Manuals
says

To install the plugin, do

yum install rubygem-smart_proxy_discovery

on Fedora and Red Hat systems

However, there is no such file named 'rubygem-smart_proxy_discovery at
http://yum.theforeman.org/plugins/1.7/el6/x86_64/ .

-= Stefan

On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal lzap@redhat.com wrote:

192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] “POST /discovery/create
HTTP/1.1” 404 431 “-” “Ruby”

Hello,

it looks like you configured image in Proxy mode against Foreman. Do you
plan to use smart-proxy for communication or not? It looks like not, in
that case set proxy.type=foreman and it should work. If you plan to use
proxy discovery plugin, change the proxy.url to your smart-proxy and
keep the “proxy” type.

We are still working on upgrade instructions.

–
Later,
Lukas #lzap Zapletal

–
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/SJiBADLHJW8/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.

Shlomi_Zadok · February 5, 2015, 11:17am

afaik, we have currently decided to remove smart_proxy_discovery plugin
support from foreman-1.7 (compatibility issues with ssl). Hopefully it will
be available on the next version of foreman.
In the meantime, it is advised to use 'proxy.type=foreman' on your
configuration (as you already did

···

On Thursday, January 29, 2015 at 9:29:08 PM UTC+2, Stefan Lasiewski wrote: > > I've started using `proxy.type=foreman` again and my nodes can register > facts again. > > Thanks, > > -= Stefan > > On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski > wrote: > >> Lukas, >> >> Thanks for that explanation. I was intending to use the Proxy Discovery >> plugin, which is why I set `proxy.type=proxy` and `proxy.url= >> http://foreman.example.org`, and I thought this worked at least once but >> I may be wrong. >> >> I figured out that never actually installed the Foreman Proxy Discovery >> plugin. It doesn't exist in the Repository. >> http://theforeman.org/plugins/foreman_discovery/2.0/#2.2ForemanProxyDiscoveryplugin >> says >> >> To install the plugin, do >>> >>> # yum install rubygem-smart_proxy_discovery >>> >>> on Fedora and Red Hat systems >>> >> >> However, there is no such file named 'rubygem-smart_proxy_discovery at >> http://yum.theforeman.org/plugins/1.7/el6/x86_64/ . >> >> -= Stefan >> >> >> On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal > > wrote: >> >>> > 192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] "POST /discovery/create >>> > HTTP/1.1" 404 431 "-" "Ruby" >>> > 192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] "POST /discovery/create >>> > HTTP/1.1" 404 431 "-" "Ruby" >>> > 192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] "POST /discovery/create >>> > HTTP/1.1" 404 431 "-" "Ruby" >>> > 192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] "POST /discovery/create >>> > HTTP/1.1" 404 431 "-" "Ruby" >>> >>> Hello, >>> >>> it looks like you configured image in Proxy mode against Foreman. Do you >>> plan to use smart-proxy for communication or not? It looks like not, in >>> that case set proxy.type=foreman and it should work. If you plan to use >>> proxy discovery plugin, change the proxy.url to your smart-proxy and >>> keep the "proxy" type. >>> >>> We are still working on upgrade instructions. >>> >>> -- >>> Later, >>> Lukas #lzap Zapletal >>> >>> -- >>> 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/SJiBADLHJW8/unsubscribe. >>> To unsubscribe from this group and all its topics, 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. >>> >> >> >

DZ1 · April 6, 2015, 1:02pm

Hi there.

I am having zero success using "proxy.type=foreman". All I get is either
SSL certificate issues "Response from Foreman 403: No client SSL
certificate supplied" with "proxy.url=httpS://myforeamanhost:8443" or
"Connection Reset by Peer" if I use http. Any useful hints you guys can
provide?

Thanks!
Foreman Version 1.7.3
Foreman-Discovery: 2.0.2

···

On Thursday, February 5, 2015 at 6:17:58 AM UTC-5, Shlomi Zadok wrote: > > afaik, we have currently decided to remove smart_proxy_discovery plugin > support from foreman-1.7 (compatibility issues with ssl). Hopefully it will > be available on the next version of foreman. > In the meantime, it is advised to use 'proxy.type=foreman' on your > configuration (as you already did :) > > On Thursday, January 29, 2015 at 9:29:08 PM UTC+2, Stefan Lasiewski wrote: >> >> I've started using `proxy.type=foreman` again and my nodes can register >> facts again. >> >> Thanks, >> >> -= Stefan >> >> On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski >> wrote: >> >>> Lukas, >>> >>> Thanks for that explanation. I was intending to use the Proxy Discovery >>> plugin, which is why I set `proxy.type=proxy` and `proxy.url= >>> http://foreman.example.org`, and I thought this worked at least once >>> but I may be wrong. >>> >>> I figured out that never actually installed the Foreman Proxy Discovery >>> plugin. It doesn't exist in the Repository. >>> http://theforeman.org/plugins/foreman_discovery/2.0/#2.2ForemanProxyDiscoveryplugin >>> says >>> >>> To install the plugin, do >>>> >>>> # yum install rubygem-smart_proxy_discovery >>>> >>>> on Fedora and Red Hat systems >>>> >>> >>> However, there is no such file named 'rubygem-smart_proxy_discovery at >>> http://yum.theforeman.org/plugins/1.7/el6/x86_64/ . >>> >>> -= Stefan >>> >>> >>> On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal >>> wrote: >>> >>>> > 192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] "POST >>>> /discovery/create >>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>> > 192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] "POST >>>> /discovery/create >>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>> > 192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] "POST >>>> /discovery/create >>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>> > 192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] "POST >>>> /discovery/create >>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>> >>>> Hello, >>>> >>>> it looks like you configured image in Proxy mode against Foreman. Do you >>>> plan to use smart-proxy for communication or not? It looks like not, in >>>> that case set proxy.type=foreman and it should work. If you plan to use >>>> proxy discovery plugin, change the proxy.url to your smart-proxy and >>>> keep the "proxy" type. >>>> >>>> We are still working on upgrade instructions. >>>> >>>> -- >>>> Later, >>>> Lukas #lzap Zapletal >>>> >>>> -- >>>> 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/SJiBADLHJW8/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, 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. >>>> >>> >>> >>

DZ1 · April 6, 2015, 7:07pm

Well it must be magic it suddenly started working.

Here is my config for the benefit of others:

"pxelinux.cfg/default" -

LABEL discovery
MENU LABEL Discovery Image fdi-image-2.1 (v1)
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop root=live:/fdi.iso
rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0
rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset
proxy.url=http://my.foremanserver proxy.type=foreman

IPAPPEND 2

"settings.yml"

:foreman_url: *https://*my.foremanserver:8443

···

On Monday, April 6, 2015 at 10:06:44 AM UTC-4, DZ wrote: > > Hi there. > > I am having zero success using "proxy.type=foreman". All I get is either > SSL certificate issues "Response from Foreman 403: No client SSL > certificate supplied" with "proxy.url=httpS://myforeamanhost:8443" or > "Connection Reset by Peer" if I use http. Any useful hints you guys can > provide? > > Thanks! > Foreman Version 1.7.3 > Foreman-Discovery: 2.0.2 > > On Thursday, February 5, 2015 at 6:17:58 AM UTC-5, Shlomi Zadok wrote: >> >> afaik, we have currently decided to remove smart_proxy_discovery plugin >> support from foreman-1.7 (compatibility issues with ssl). Hopefully it will >> be available on the next version of foreman. >> In the meantime, it is advised to use 'proxy.type=foreman' on your >> configuration (as you already did :) >> >> On Thursday, January 29, 2015 at 9:29:08 PM UTC+2, Stefan Lasiewski wrote: >>> >>> I've started using `proxy.type=foreman` again and my nodes can register >>> facts again. >>> >>> Thanks, >>> >>> -= Stefan >>> >>> On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski >>> wrote: >>> >>>> Lukas, >>>> >>>> Thanks for that explanation. I was intending to use the Proxy Discovery >>>> plugin, which is why I set `proxy.type=proxy` and `proxy.url= >>>> http://foreman.example.org`, and I thought this worked at least once >>>> but I may be wrong. >>>> >>>> I figured out that never actually installed the Foreman Proxy Discovery >>>> plugin. It doesn't exist in the Repository. >>>> http://theforeman.org/plugins/foreman_discovery/2.0/#2.2ForemanProxyDiscoveryplugin >>>> says >>>> >>>> To install the plugin, do >>>>> >>>>> # yum install rubygem-smart_proxy_discovery >>>>> >>>>> on Fedora and Red Hat systems >>>>> >>>> >>>> However, there is no such file named 'rubygem-smart_proxy_discovery at >>>> http://yum.theforeman.org/plugins/1.7/el6/x86_64/ . >>>> >>>> -= Stefan >>>> >>>> >>>> On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal >>>> wrote: >>>> >>>>> > 192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] "POST >>>>> /discovery/create >>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>> > 192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] "POST >>>>> /discovery/create >>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>> > 192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] "POST >>>>> /discovery/create >>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>> > 192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] "POST >>>>> /discovery/create >>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>> >>>>> Hello, >>>>> >>>>> it looks like you configured image in Proxy mode against Foreman. Do >>>>> you >>>>> plan to use smart-proxy for communication or not? It looks like not, in >>>>> that case set proxy.type=foreman and it should work. If you plan to use >>>>> proxy discovery plugin, change the proxy.url to your smart-proxy and >>>>> keep the "proxy" type. >>>>> >>>>> We are still working on upgrade instructions. >>>>> >>>>> -- >>>>> Later, >>>>> Lukas #lzap Zapletal >>>>> >>>>> -- >>>>> 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/SJiBADLHJW8/unsubscribe >>>>> . >>>>> To unsubscribe from this group and all its topics, 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. >>>>> >>>> >>>> >>>

Miguel_Cantu · June 8, 2015, 7:13pm

I'm seeing the same error, but am using the IP and port as the proxy.url in
the kernel paramters.

LABEL discovery
MENU LABEL (discovery)
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop
root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0
rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset
proxy.url=http://<my-ip>:8443 proxy.type=proxy fdi.rootpw=password
IPAPPEND 2

All I see is "Connection reset by peer" in the fdi syslog.
I get the same thing when proxy.type=foreman

Can anybody help?

···

On Monday, April 6, 2015 at 2:07:52 PM UTC-5, DZ wrote: > > Well it must be magic :-) it suddenly started working. > > Here is my config for the benefit of others: > > *"pxelinux.cfg/default*" - > > LABEL discovery > MENU LABEL Discovery Image fdi-image-2.1 (v1) > MENU DEFAULT > KERNEL boot/fdi-image/vmlinuz0 > APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop root=live:/fdi.iso > rootfstype=auto ro rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 > rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset *proxy.url=http://my.foremanserver > * proxy.type=*foreman* > > IPAPPEND 2 > > *"settings.yml"* > > :foreman_url: *https://**my.foremanserver:8443* > > > > On Monday, April 6, 2015 at 10:06:44 AM UTC-4, DZ wrote: >> >> Hi there. >> >> I am having zero success using "proxy.type=foreman". All I get is either >> SSL certificate issues "Response from Foreman 403: No client SSL >> certificate supplied" with "proxy.url=httpS://myforeamanhost:8443" or >> "Connection Reset by Peer" if I use http. Any useful hints you guys can >> provide? >> >> Thanks! >> Foreman Version 1.7.3 >> Foreman-Discovery: 2.0.2 >> >> On Thursday, February 5, 2015 at 6:17:58 AM UTC-5, Shlomi Zadok wrote: >>> >>> afaik, we have currently decided to remove smart_proxy_discovery plugin >>> support from foreman-1.7 (compatibility issues with ssl). Hopefully it will >>> be available on the next version of foreman. >>> In the meantime, it is advised to use 'proxy.type=foreman' on your >>> configuration (as you already did :) >>> >>> On Thursday, January 29, 2015 at 9:29:08 PM UTC+2, Stefan Lasiewski >>> wrote: >>>> >>>> I've started using `proxy.type=foreman` again and my nodes can register >>>> facts again. >>>> >>>> Thanks, >>>> >>>> -= Stefan >>>> >>>> On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski >>> > wrote: >>>> >>>>> Lukas, >>>>> >>>>> Thanks for that explanation. I was intending to use the Proxy >>>>> Discovery plugin, which is why I set `proxy.type=proxy` and `proxy.url= >>>>> http://foreman.example.org`, and I thought this worked at least once >>>>> but I may be wrong. >>>>> >>>>> I figured out that never actually installed the Foreman Proxy >>>>> Discovery plugin. It doesn't exist in the Repository. >>>>> http://theforeman.org/plugins/foreman_discovery/2.0/#2.2ForemanProxyDiscoveryplugin >>>>> says >>>>> >>>>> To install the plugin, do >>>>>> >>>>>> # yum install rubygem-smart_proxy_discovery >>>>>> >>>>>> on Fedora and Red Hat systems >>>>>> >>>>> >>>>> However, there is no such file named 'rubygem-smart_proxy_discovery at >>>>> http://yum.theforeman.org/plugins/1.7/el6/x86_64/ . >>>>> >>>>> -= Stefan >>>>> >>>>> >>>>> On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal >>>>> wrote: >>>>> >>>>>> > 192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] "POST >>>>>> /discovery/create >>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>> > 192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] "POST >>>>>> /discovery/create >>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>> > 192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] "POST >>>>>> /discovery/create >>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>> > 192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] "POST >>>>>> /discovery/create >>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>> >>>>>> Hello, >>>>>> >>>>>> it looks like you configured image in Proxy mode against Foreman. Do >>>>>> you >>>>>> plan to use smart-proxy for communication or not? It looks like not, >>>>>> in >>>>>> that case set proxy.type=foreman and it should work. If you plan to >>>>>> use >>>>>> proxy discovery plugin, change the proxy.url to your smart-proxy and >>>>>> keep the "proxy" type. >>>>>> >>>>>> We are still working on upgrade instructions. >>>>>> >>>>>> -- >>>>>> Later, >>>>>> Lukas #lzap Zapletal >>>>>> >>>>>> -- >>>>>> 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/SJiBADLHJW8/unsubscribe >>>>>> . >>>>>> To unsubscribe from this group and all its topics, 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. >>>>>> >>>>> >>>>> >>>>

ohadlevy · June 8, 2015, 7:20pm

what did you configure as foreman url? it should be the URL that foreman is
reachable, not the proxy?

Ohad

···

On Mon, Jun 8, 2015 at 10:13 PM, Miguel Cantu wrote:

I’m seeing the same error, but am using the IP and port as the proxy.url
in the kernel paramters.

LABEL discovery
MENU LABEL (discovery)
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop
root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0
rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset
proxy.url=http://:8443 proxy.type=proxy fdi.rootpw=password
IPAPPEND 2

All I see is “Connection reset by peer” in the fdi syslog.
I get the same thing when proxy.type=foreman

Can anybody help?

On Monday, April 6, 2015 at 2:07:52 PM UTC-5, DZ wrote:

Well it must be magic it suddenly started working.

Here is my config for the benefit of others:

"pxelinux.cfg/default" -

LABEL discovery
MENU LABEL Discovery Image fdi-image-2.1 (v1)
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop
root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0
rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset proxy.url=http://my.foremanserver
http://my.foremanserver proxy.type=foreman

IPAPPEND 2

“settings.yml”

:foreman_url: *https://*my.foremanserver:8443

On Monday, April 6, 2015 at 10:06:44 AM UTC-4, DZ wrote:

Hi there.

I am having zero success using “proxy.type=foreman”. All I get is either
SSL certificate issues “Response from Foreman 403: No client SSL
certificate supplied” with “proxy.url=httpS://myforeamanhost:8443” or
"Connection Reset by Peer" if I use http. Any useful hints you guys can
provide?

Thanks!
Foreman Version 1.7.3
Foreman-Discovery: 2.0.2

On Thursday, February 5, 2015 at 6:17:58 AM UTC-5, Shlomi Zadok wrote:

afaik, we have currently decided to remove smart_proxy_discovery plugin
support from foreman-1.7 (compatibility issues with ssl). Hopefully it will
be available on the next version of foreman.
In the meantime, it is advised to use ‘proxy.type=foreman’ on your
configuration (as you already did

On Thursday, January 29, 2015 at 9:29:08 PM UTC+2, Stefan Lasiewski >>>> wrote:

I’ve started using proxy.type=foreman again and my nodes can
register facts again.

Thanks,

-= Stefan

On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski < >>>>> ste...@stefanco.com> wrote:

Lukas,

Thanks for that explanation. I was intending to use the Proxy
Discovery plugin, which is why I set proxy.type=proxy and proxy.url= http://foreman.example.org, and I thought this worked at least once
but I may be wrong.

I figured out that never actually installed the Foreman Proxy
Discovery plugin. It doesn’t exist in the Repository.
Foreman :: Plugin Manuals
says

To install the plugin, do

yum install rubygem-smart_proxy_discovery

on Fedora and Red Hat systems

However, there is no such file named 'rubygem-smart_proxy_discovery
at http://yum.theforeman.org/plugins/1.7/el6/x86_64/ .

-= Stefan

On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal lz...@redhat.com >>>>>> wrote:

192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” “Ruby”

Hello,

it looks like you configured image in Proxy mode against Foreman. Do
you
plan to use smart-proxy for communication or not? It looks like not,
in
that case set proxy.type=foreman and it should work. If you plan to
use
proxy discovery plugin, change the proxy.url to your smart-proxy and
keep the “proxy” type.

We are still working on upgrade instructions.

–
Later,
Lukas #lzap Zapletal

–
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/SJiBADLHJW8/unsubscribe
.
To unsubscribe from this group and all its topics, 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.

–
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.

Miguel_Cantu · June 8, 2015, 7:23pm

foreman_url=https://<foreman-ip>:8443

That's in my /etc/foreman-proxy/settings.yml

···

On Monday, June 8, 2015 at 2:20:22 PM UTC-5, ohad wrote: > > what did you configure as foreman url? it should be the URL that foreman > is reachable, not the proxy? > > Ohad > > On Mon, Jun 8, 2015 at 10:13 PM, Miguel Cantu > wrote: > >> I'm seeing the same error, but am using the IP and port as the proxy.url >> in the kernel paramters. >> >> LABEL discovery >> MENU LABEL (discovery) >> MENU DEFAULT >> KERNEL boot/fdi-image/vmlinuz0 >> APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop >> root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0 >> rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset >> proxy.url=http://:8443 proxy.type=proxy fdi.rootpw=password >> IPAPPEND 2 >> >> All I see is "Connection reset by peer" in the fdi syslog. >> I get the same thing when proxy.type=foreman >> >> Can anybody help? >> >> On Monday, April 6, 2015 at 2:07:52 PM UTC-5, DZ wrote: >>> >>> Well it must be magic :-) it suddenly started working. >>> >>> Here is my config for the benefit of others: >>> >>> *"pxelinux.cfg/default*" - >>> >>> LABEL discovery >>> MENU LABEL Discovery Image fdi-image-2.1 (v1) >>> MENU DEFAULT >>> KERNEL boot/fdi-image/vmlinuz0 >>> APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop >>> root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0 >>> rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset *proxy.url=http://my.foremanserver >>> * proxy.type=*foreman* >>> >>> IPAPPEND 2 >>> >>> *"settings.yml"* >>> >>> :foreman_url: *https://**my.foremanserver:8443* >>> >>> >>> >>> On Monday, April 6, 2015 at 10:06:44 AM UTC-4, DZ wrote: >>>> >>>> Hi there. >>>> >>>> I am having zero success using "proxy.type=foreman". All I get is >>>> either SSL certificate issues "Response from Foreman 403: No client SSL >>>> certificate supplied" with "proxy.url=httpS://myforeamanhost:8443" or >>>> "Connection Reset by Peer" if I use http. Any useful hints you guys can >>>> provide? >>>> >>>> Thanks! >>>> Foreman Version 1.7.3 >>>> Foreman-Discovery: 2.0.2 >>>> >>>> On Thursday, February 5, 2015 at 6:17:58 AM UTC-5, Shlomi Zadok wrote: >>>>> >>>>> afaik, we have currently decided to remove smart_proxy_discovery >>>>> plugin support from foreman-1.7 (compatibility issues with ssl). Hopefully >>>>> it will be available on the next version of foreman. >>>>> In the meantime, it is advised to use 'proxy.type=foreman' on your >>>>> configuration (as you already did :) >>>>> >>>>> On Thursday, January 29, 2015 at 9:29:08 PM UTC+2, Stefan Lasiewski >>>>> wrote: >>>>>> >>>>>> I've started using `proxy.type=foreman` again and my nodes can >>>>>> register facts again. >>>>>> >>>>>> Thanks, >>>>>> >>>>>> -= Stefan >>>>>> >>>>>> On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski < >>>>>> ste...@stefanco.com> wrote: >>>>>> >>>>>>> Lukas, >>>>>>> >>>>>>> Thanks for that explanation. I was intending to use the Proxy >>>>>>> Discovery plugin, which is why I set `proxy.type=proxy` and `proxy.url= >>>>>>> http://foreman.example.org`, and I thought this worked at least >>>>>>> once but I may be wrong. >>>>>>> >>>>>>> I figured out that never actually installed the Foreman Proxy >>>>>>> Discovery plugin. It doesn't exist in the Repository. >>>>>>> http://theforeman.org/plugins/foreman_discovery/2.0/#2.2ForemanProxyDiscoveryplugin >>>>>>> says >>>>>>> >>>>>>> To install the plugin, do >>>>>>>> >>>>>>>> # yum install rubygem-smart_proxy_discovery >>>>>>>> >>>>>>>> on Fedora and Red Hat systems >>>>>>>> >>>>>>> >>>>>>> However, there is no such file named 'rubygem-smart_proxy_discovery >>>>>>> at http://yum.theforeman.org/plugins/1.7/el6/x86_64/ . >>>>>>> >>>>>>> -= Stefan >>>>>>> >>>>>>> >>>>>>> On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal >>>>>>> wrote: >>>>>>> >>>>>>>> > 192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] "POST >>>>>>>> /discovery/create >>>>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>>>> > 192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] "POST >>>>>>>> /discovery/create >>>>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>>>> > 192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] "POST >>>>>>>> /discovery/create >>>>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>>>> > 192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] "POST >>>>>>>> /discovery/create >>>>>>>> > HTTP/1.1" 404 431 "-" "Ruby" >>>>>>>> >>>>>>>> Hello, >>>>>>>> >>>>>>>> it looks like you configured image in Proxy mode against Foreman. >>>>>>>> Do you >>>>>>>> plan to use smart-proxy for communication or not? It looks like >>>>>>>> not, in >>>>>>>> that case set proxy.type=foreman and it should work. If you plan to >>>>>>>> use >>>>>>>> proxy discovery plugin, change the proxy.url to your smart-proxy and >>>>>>>> keep the "proxy" type. >>>>>>>> >>>>>>>> We are still working on upgrade instructions. >>>>>>>> >>>>>>>> -- >>>>>>>> Later, >>>>>>>> Lukas #lzap Zapletal >>>>>>>> >>>>>>>> -- >>>>>>>> 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/SJiBADLHJW8/unsubscribe >>>>>>>> . >>>>>>>> To unsubscribe from this group and all its topics, 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. >>>>>>>> >>>>>>> >>>>>>> >>>>>> -- >> 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. >> > >

ohadlevy · June 8, 2015, 7:33pm

> foreman_url=https://<foreman-ip>:8443
>
why 8443? thats usually the proxy?

Ohad

···

On Mon, Jun 8, 2015 at 10:23 PM, Miguel Cantu wrote:

That’s in my /etc/foreman-proxy/settings.yml

On Monday, June 8, 2015 at 2:20:22 PM UTC-5, ohad wrote:

what did you configure as foreman url? it should be the URL that foreman
is reachable, not the proxy?

Ohad

On Mon, Jun 8, 2015 at 10:13 PM, Miguel Cantu mushro...@gmail.com >> wrote:

I’m seeing the same error, but am using the IP and port as the proxy.url
in the kernel paramters.

LABEL discovery
MENU LABEL (discovery)
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop
root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0
rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset
proxy.url=http://:8443 proxy.type=proxy fdi.rootpw=password
IPAPPEND 2

All I see is “Connection reset by peer” in the fdi syslog.
I get the same thing when proxy.type=foreman

Can anybody help?

On Monday, April 6, 2015 at 2:07:52 PM UTC-5, DZ wrote:

Well it must be magic it suddenly started working.

Here is my config for the benefit of others:

"pxelinux.cfg/default" -

LABEL discovery
MENU LABEL Discovery Image fdi-image-2.1 (v1)
MENU DEFAULT
KERNEL boot/fdi-image/vmlinuz0
APPEND initrd=boot/fdi-image/initrd0.img rootflags=loop
root=live:/fdi.iso rootfstype=auto ro rd.live.image acpi=force rd.luks=0
rd.md=0 rd.dm=0 rd.lvm=0 rd.bootif=0 rd.neednet=0 nomodeset proxy.url=http://my.foremanserver
http://my.foremanserver proxy.type=foreman

IPAPPEND 2

“settings.yml”

:foreman_url: *https://*my.foremanserver:8443

On Monday, April 6, 2015 at 10:06:44 AM UTC-4, DZ wrote:

Hi there.

I am having zero success using “proxy.type=foreman”. All I get is
either SSL certificate issues “Response from Foreman 403: No client SSL
certificate supplied” with “proxy.url=httpS://myforeamanhost:8443” or
"Connection Reset by Peer" if I use http. Any useful hints you guys can
provide?

Thanks!
Foreman Version 1.7.3
Foreman-Discovery: 2.0.2

On Thursday, February 5, 2015 at 6:17:58 AM UTC-5, Shlomi Zadok wrote:

afaik, we have currently decided to remove smart_proxy_discovery
plugin support from foreman-1.7 (compatibility issues with ssl). Hopefully
it will be available on the next version of foreman.
In the meantime, it is advised to use ‘proxy.type=foreman’ on your
configuration (as you already did

On Thursday, January 29, 2015 at 9:29:08 PM UTC+2, Stefan Lasiewski >>>>>> wrote:

I’ve started using proxy.type=foreman again and my nodes can
register facts again.

Thanks,

-= Stefan

On Thu, Jan 29, 2015 at 11:27 AM, Stefan Lasiewski < >>>>>>> ste...@stefanco.com> wrote:

Lukas,

Thanks for that explanation. I was intending to use the Proxy
Discovery plugin, which is why I set proxy.type=proxy and proxy.url= http://foreman.example.org, and I thought this worked at least
once but I may be wrong.

I figured out that never actually installed the Foreman Proxy
Discovery plugin. It doesn’t exist in the Repository.
Foreman :: Plugin Manuals
says

To install the plugin, do

yum install rubygem-smart_proxy_discovery

on Fedora and Red Hat systems

However, there is no such file named 'rubygem-smart_proxy_discovery
at http://yum.theforeman.org/plugins/1.7/el6/x86_64/ .

-= Stefan

On Thu, Jan 29, 2015 at 2:04 AM, Lukas Zapletal lz...@redhat.com >>>>>>>> wrote:

192.168.20.221 - - [28/Jan/2015:17:38:22 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.222 - - [28/Jan/2015:17:38:43 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.220 - - [28/Jan/2015:17:38:52 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” "Ruby"
192.168.20.221 - - [28/Jan/2015:17:38:53 -0800] “POST
/discovery/create
HTTP/1.1” 404 431 “-” “Ruby”

Hello,

it looks like you configured image in Proxy mode against Foreman.
Do you
plan to use smart-proxy for communication or not? It looks like
not, in
that case set proxy.type=foreman and it should work. If you plan
to use
proxy discovery plugin, change the proxy.url to your smart-proxy
and
keep the “proxy” type.

We are still working on upgrade instructions.

–
Later,
Lukas #lzap Zapletal

–
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/SJiBADLHJW8/unsubscribe
.
To unsubscribe from this group and all its topics, 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.

–
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.

–
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.