> Dear ALL,
>
> how was the problem discribed in this post ->
> Bug #1498: unattended provisioning with foreman login enabled - Foreman solved? My pxe default is
> looking like this
>
> default linux label linux kernel <%= @kernel > append vga=788
> initrd=<= @initrd > install auto=true priority=critical edd=off
> preseed/url=http://xxxx.xxxx.xxxx/unattended/provision?spoof=<= ip
> %> –
You shouldn't be using ?spoof for actual installs - its for checking
the templates are right.
> This is working fine as long as i have disabled login.
>
> For my understanding i thought changing it to
>
> default linux label linux kernel <%= @kernel > append vga=788
> initrd=<= @initrd %> install auto=true priority=critical edd=off
> preseed/url=http://xxxx.xxxx.xxxx/unattended/provision –
>
> would solve my problem. But it didn't …
Sounds like you have a problem with your template generation. This is
usually related to sudo permissions on the proxy. Check your proxy
logs for any errors when the host requests it's provision file.
> I had similar problem like Daniel,
> I removed the "spoof" from the URL, but now I don't get the KS file.
> foreman says something like:
> "Failed to add <my server> to autosign file: 404 Resource Not Found"
>
You should double check the log on your proxy, there is a good chance you
have some sort of permissions error.
>
>
the odd part is that in the host configuration, I see the correct smart
···
On Wed, Sep 5, 2012 at 7:55 AM, Shmiti wrote:
> proxy (I only have 1 with puppetCA and puppet)
> and I do manage to manually add, via foreman, values to the autosign.
>
> On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
>>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 29/06/12 10:52, Daniel Verniers wrote:
>> > Dear ALL,
>> >
>> > how was the problem discribed in this post ->
>> > http://theforeman.org/issues/**1498 solved? My pxe default is
>> > looking like this
>> >
>> > default linux label linux kernel <%= @kernel > append vga=788
>> > initrd=<= @initrd > install auto=true priority=critical edd=off
>> > preseed/url=http://xxxx.xxxx.**xxxx/unattended/provision?**spoof=<=
>> ip
>> > %> --
>>
>> You shouldn't be using ?spoof for actual installs - its for checking
>> the templates are right.
>>
>> > This is working fine as long as i have disabled login.
>> >
>> > For my understanding i thought changing it to
>> >
>> > default linux label linux kernel <%= @kernel > append vga=788
>> > initrd=<= @initrd %> install auto=true priority=critical edd=off
>> > preseed/url=http://xxxx.xxxx.**xxxx/unattended/provision--
>> >
>> > would solve my problem. But it didn't ...
>>
>> Sounds like you have a problem with your template generation. This is
>> usually related to sudo permissions on the proxy. Check your proxy
>> logs for any errors when the host requests it's provision file.
>>
>> Cheers,
>> Greg
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v2.0.19 (GNU/Linux)
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>
>> iEYEARECAAYFAk/**tjmcACgkQ8O7RN8oK65NwnwCgnhgwB**NQjc/zzC6lJIknWMsv0
>> /**l0AnApEsAjFcZNQHrV5eOkovp7Qbqi**t
>> =p/WN
>> -----END PGP SIGNATURE-----
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/foreman-users/-/_hGIDFcVtPQJ.
>
> To post to this group, send email to foreman-users@googlegroups.com.
> To unsubscribe from this group, send email to
> foreman-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/foreman-users?hl=en.
>
I have, on both proxies, nothing there.
I think it may be caused since I moved the puppet to another proxy and
there is some inconsistency in the DB?
it seems to me that it's internal in the forman itself and it can't find
the right proxy to address to, question is how can I verify that?
···
On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
>
>
>
> On Wed, Sep 5, 2012 at 7:55 AM, Shmiti <el...@shmiti.com >wrote:
>
>> I had similar problem like Daniel,
>> I removed the "spoof" from the URL, but now I don't get the KS file.
>> foreman says something like:
>> "Failed to add to autosign file: 404 Resource Not Found"
>>
>
> You should double check the log on your proxy, there is a good chance you
> have some sort of permissions error.
>
>>
>>
> the odd part is that in the host configuration, I see the correct smart
>> proxy (I only have 1 with puppetCA and puppet)
>> and I do manage to manually add, via foreman, values to the autosign.
>>
>> On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
>>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> On 29/06/12 10:52, Daniel Verniers wrote:
>>> > Dear ALL,
>>> >
>>> > how was the problem discribed in this post ->
>>> > http://theforeman.org/issues/**1498solved? My pxe default is
>>> > looking like this
>>> >
>>> > default linux label linux kernel <%= @kernel > append vga=788
>>> > initrd=<= @initrd > install auto=true priority=critical edd=off
>>> > preseed/url=http://xxxx.xxxx.**xxxx/unattended/provision?**spoof=<=
>>> ip
>>> > %> --
>>>
>>> You shouldn't be using ?spoof for actual installs - its for checking
>>> the templates are right.
>>>
>>> > This is working fine as long as i have disabled login.
>>> >
>>> > For my understanding i thought changing it to
>>> >
>>> > default linux label linux kernel <%= @kernel > append vga=788
>>> > initrd=<= @initrd %> install auto=true priority=critical edd=off
>>> > preseed/url=http://xxxx.xxxx.**xxxx/unattended/provision--
>>> >
>>> > would solve my problem. But it didn't ...
>>>
>>> Sounds like you have a problem with your template generation. This is
>>> usually related to sudo permissions on the proxy. Check your proxy
>>> logs for any errors when the host requests it's provision file.
>>>
>>> Cheers,
>>> Greg
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v2.0.19 (GNU/Linux)
>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>
>>> iEYEARECAAYFAk/**tjmcACgkQ8O7RN8oK65NwnwCgnhgwB**NQjc/zzC6lJIknWMsv0
>>> /**l0AnApEsAjFcZNQHrV5eOkovp7Qbqi**t
>>> =p/WN
>>> -----END PGP SIGNATURE-----
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/foreman-users/-/_hGIDFcVtPQJ.
>>
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> foreman-user...@googlegroups.com .
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
> I have, on both proxies, nothing there.
> I think it may be caused since I moved the puppet to another proxy and
> there is some inconsistency in the DB?
> it seems to me that it's internal in the forman itself and it can't find
> the right proxy to address to, question is how can I verify that?
>
you can select the proxy to use per host (just edit the host and select
it).
you can increase the log level to debug in the proxy config
(/etc/foreman-proxy/settings.yml)
Ohad
···
On Wed, Sep 5, 2012 at 9:36 AM, Shmiti wrote:
On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
I had similar problem like Daniel,
I removed the “spoof” from the URL, but now I don’t get the KS file.
foreman says something like:
“Failed to add to autosign file: 404 Resource Not Found”
You should double check the log on your proxy, there is a good chance you
have some sort of permissions error.
the odd part is that in the host configuration, I see the correct smart
proxy (I only have 1 with puppetCA and puppet)
and I do manage to manually add, via foreman, values to the autosign.
On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd > install auto=true priority=critical edd=off
preseed/url=http://xxxx.xxxx.xxxx/unattended/provision?spoof=http://xxxx.xxxx.xxxx/unattended/provision?spoof=<=
ip
%> –
You shouldn’t be using ?spoof for actual installs - its for checking
the templates are right.
This is working fine as long as i have disabled login.
For my understanding i thought changing it to
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd %> install auto=true priority=critical edd=off
preseed/url=http://xxxx.xxxx.xxxx/unattended/provisionhttp://xxxx.xxxx.xxxx/unattended/provision–
would solve my problem. But it didn’t …
Sounds like you have a problem with your template generation. This is
usually related to sudo permissions on the proxy. Check your proxy
logs for any errors when the host requests it’s provision file.
Cheers,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
The proxy IS selected, put the proxy on debug, also put a sniffer on the
proxy server, there is no request arriving to the proxy.
how can I increase the debug in the forman itself?
···
On Wednesday, September 5, 2012 9:46:49 AM UTC+3, ohad wrote:
>
>
>
> On Wed, Sep 5, 2012 at 9:36 AM, Shmiti <el...@shmiti.com >wrote:
>
>> I have, on both proxies, nothing there.
>> I think it may be caused since I moved the puppet to another proxy and
>> there is some inconsistency in the DB?
>> it seems to me that it's internal in the forman itself and it can't find
>> the right proxy to address to, question is how can I verify that?
>>
>
> 1. you can select the proxy to use per host (just edit the host and select
> it).
> 2. you can increase the log level to debug in the proxy config
> (/etc/foreman-proxy/settings.yml)
>
> Ohad
>
>>
>> On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
>>>
>>>
>>>
>>> On Wed, Sep 5, 2012 at 7:55 AM, Shmiti wrote:
>>>
>>>> I had similar problem like Daniel,
>>>> I removed the "spoof" from the URL, but now I don't get the KS file.
>>>> foreman says something like:
>>>> "Failed to add to autosign file: 404 Resource Not Found"
>>>>
>>>
>>> You should double check the log on your proxy, there is a good chance
>>> you have some sort of permissions error.
>>>
>>>>
>>>>
>>> the odd part is that in the host configuration, I see the correct smart
>>>> proxy (I only have 1 with puppetCA and puppet)
>>>> and I do manage to manually add, via foreman, values to the autosign.
>>>>
>>>> On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
>>>>>
>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>> Hash: SHA1
>>>>>
>>>>> On 29/06/12 10:52, Daniel Verniers wrote:
>>>>> > Dear ALL,
>>>>> >
>>>>> > how was the problem discribed in this post ->
>>>>> > http://theforeman.org/issues/**1**498solved? My pxe default is
>>>>> > looking like this
>>>>> >
>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>> > initrd=<= @initrd > install auto=true priority=critical edd=off
>>>>> > preseed/url=http://xxxx.xxxx.**x**xxx/unattended/provision?**spoof**
>>>>> = <= ip
>>>>> > %> --
>>>>>
>>>>> You shouldn't be using ?spoof for actual installs - its for checking
>>>>> the templates are right.
>>>>>
>>>>> > This is working fine as long as i have disabled login.
>>>>> >
>>>>> > For my understanding i thought changing it to
>>>>> >
>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>> > initrd=<= @initrd %> install auto=true priority=critical edd=off
>>>>> > preseed/url=http://xxxx.xxxx.**x**xxx/unattended/provision--
>>>>> >
>>>>> > would solve my problem. But it didn't ...
>>>>>
>>>>> Sounds like you have a problem with your template generation. This is
>>>>> usually related to sudo permissions on the proxy. Check your proxy
>>>>> logs for any errors when the host requests it's provision file.
>>>>>
>>>>> Cheers,
>>>>> Greg
>>>>> -----BEGIN PGP SIGNATURE-----
>>>>> Version: GnuPG v2.0.19 (GNU/Linux)
>>>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>>>
>>>>> iEYEARECAAYFAk/**tjmcACgkQ8O7RN8**oK65NwnwCgnhgwB**NQjc/**zzC6lJIknWMsv0
>>>>>
>>>>> /**l0AnApEsAjFcZNQHrV5eOkovp7Qbq**i**t
>>>>> =p/WN
>>>>> -----END PGP SIGNATURE-----
>>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To view this discussion on the web visit https://groups.google.com/d/**
>>>> msg/foreman-users/-/_**hGIDFcVtPQJ
>>>> .
>>>>
>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>> googlegroups.com.
>>>>
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/foreman-users?hl=en
>>>> .
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/foreman-users/-/TiKYEwRiYMQJ.
>>
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> foreman-user...@googlegroups.com .
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
> The proxy IS selected, put the proxy on debug, also put a sniffer on the
> proxy server, there is no request arriving to the proxy.
> how can I increase the debug in the forman itself?
>
I have, on both proxies, nothing there.
I think it may be caused since I moved the puppet to another proxy and
there is some inconsistency in the DB?
it seems to me that it’s internal in the forman itself and it can’t find
the right proxy to address to, question is how can I verify that?
you can select the proxy to use per host (just edit the host and
select it).
you can increase the log level to debug in the proxy config
(/etc/foreman-proxy/settings.**yml)
Ohad
On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
I had similar problem like Daniel,
I removed the “spoof” from the URL, but now I don’t get the KS file.
foreman says something like:
“Failed to add to autosign file: 404 Resource Not Found”
You should double check the log on your proxy, there is a good chance
you have some sort of permissions error.
the odd part is that in the host configuration, I see the correct smart
proxy (I only have 1 with puppetCA and puppet)
and I do manage to manually add, via foreman, values to the autosign.
On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd > install auto=true priority=critical edd=off
preseed/url=http://xxxx.xxxx.x****xxx/unattended/provision?
spoof****= http://xxxx.xxxx.xxxx/unattended/provision?spoof=<= ip
%> –
You shouldn’t be using ?spoof for actual installs - its for checking
the templates are right.
This is working fine as long as i have disabled login.
For my understanding i thought changing it to
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd %> install auto=true priority=critical edd=off
preseed/url=http://xxxx.xxxx.**x****xxx/unattended/provisionhttp://xxxx.xxxx.xxxx/unattended/provision–
would solve my problem. But it didn’t …
Sounds like you have a problem with your template generation. This is
usually related to sudo permissions on the proxy. Check your proxy
logs for any errors when the host requests it’s provision file.
Cheers,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
With the debugging I've found that the settings in the host pointed to the
wrong proxy, which is odd since in the UI, I couldn't pick a proxy, only 1
is connected to puppetca.
I changed the value directly via the DB and it's now ok, checked the UI and
it's still showing the same proxy…
it's odd, any suggestions?
···
On Wednesday, September 5, 2012 9:55:10 AM UTC+3, ohad wrote:
>
>
>
> On Wed, Sep 5, 2012 at 9:51 AM, Shmiti <el...@shmiti.com >wrote:
>
>> The proxy IS selected, put the proxy on debug, also put a sniffer on the
>> proxy server, there is no request arriving to the proxy.
>> how can I increase the debug in the forman itself?
>>
>
> see
> http://theforeman.org/projects/foreman/wiki/Troubleshooting#How-do-I-enable-debugging
> Ohad
>
>>
>> On Wednesday, September 5, 2012 9:46:49 AM UTC+3, ohad wrote:
>>
>>>
>>>
>>> On Wed, Sep 5, 2012 at 9:36 AM, Shmiti wrote:
>>>
>>>> I have, on both proxies, nothing there.
>>>> I think it may be caused since I moved the puppet to another proxy and
>>>> there is some inconsistency in the DB?
>>>> it seems to me that it's internal in the forman itself and it can't
>>>> find the right proxy to address to, question is how can I verify that?
>>>>
>>>
>>> 1. you can select the proxy to use per host (just edit the host and
>>> select it).
>>> 2. you can increase the log level to debug in the proxy config
>>> (/etc/foreman-proxy/settings.**yml)
>>>
>>> Ohad
>>>
>>>>
>>>> On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 5, 2012 at 7:55 AM, Shmiti wrote:
>>>>>
>>>>>> I had similar problem like Daniel,
>>>>>> I removed the "spoof" from the URL, but now I don't get the KS file.
>>>>>> foreman says something like:
>>>>>> "Failed to add to autosign file: 404 Resource Not Found"
>>>>>>
>>>>>
>>>>> You should double check the log on your proxy, there is a good chance
>>>>> you have some sort of permissions error.
>>>>>
>>>>>>
>>>>>>
>>>>> the odd part is that in the host configuration, I see
>>>>>> the correct smart proxy (I only have 1 with puppetCA and puppet)
>>>>>> and I do manage to manually add, via foreman, values to the autosign.
>>>>>>
>>>>>> On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
>>>>>>>
>>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>>> Hash: SHA1
>>>>>>>
>>>>>>> On 29/06/12 10:52, Daniel Verniers wrote:
>>>>>>> > Dear ALL,
>>>>>>> >
>>>>>>> > how was the problem discribed in this post ->
>>>>>>> > http://theforeman.org/issues/**1****498solved? My pxe default is
>>>>>>> > looking like this
>>>>>>> >
>>>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>>>> > initrd=<= @initrd > install auto=true priority=critical edd=off
>>>>>>> > preseed/url=http://xxxx.xxxx.**x****xxx/unattended/provision?**
>>>>>>> spoof****= <= ip
>>>>>>> > %> --
>>>>>>>
>>>>>>> You shouldn't be using ?spoof for actual installs - its for checking
>>>>>>> the templates are right.
>>>>>>>
>>>>>>> > This is working fine as long as i have disabled login.
>>>>>>> >
>>>>>>> > For my understanding i thought changing it to
>>>>>>> >
>>>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>>>> > initrd=<= @initrd %> install auto=true priority=critical edd=off
>>>>>>> > preseed/url=http://xxxx.xxxx.**x****xxx/unattended/provision--
>>>>>>> >
>>>>>>> > would solve my problem. But it didn't ...
>>>>>>>
>>>>>>> Sounds like you have a problem with your template generation. This
>>>>>>> is
>>>>>>> usually related to sudo permissions on the proxy. Check your proxy
>>>>>>> logs for any errors when the host requests it's provision file.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Greg
>>>>>>> -----BEGIN PGP SIGNATURE-----
>>>>>>> Version: GnuPG v2.0.19 (GNU/Linux)
>>>>>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>>>>>
>>>>>>> iEYEARECAAYFAk/**tjmcACgkQ8O7RN8****oK65NwnwCgnhgwB**NQjc/**
>>>>>>> zzC6lJIknW**Msv0
>>>>>>> /**l0AnApEsAjFcZNQHrV5eOkovp7Qbq****i**t
>>>>>>> =p/WN
>>>>>>> -----END PGP SIGNATURE-----
>>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Foreman users" group.
>>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>>> **ms**g/foreman-users/-/_**hGIDFcVtPQJ
>>>>>> **.
>>>>>>
>>>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>>>> googlegroups.**com.
>>>>>>
>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>> group**/foreman-users?hl=en
>>>>>> .
>>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To view this discussion on the web visit https://groups.google.com/d/**
>>>> msg/foreman-users/-/**TiKYEwRiYMQJ
>>>> .
>>>>
>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>> googlegroups.com.
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/foreman-users?hl=en
>>>> .
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/foreman-users/-/IvhGNnzJXT8J.
>>
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> foreman-user...@googlegroups.com .
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
> With the debugging I've found that the settings in the host pointed to the
> wrong proxy, which is odd since in the UI, I couldn't pick a proxy, only 1
> is connected to puppetca.
> I changed the value directly via the DB and it's now ok, checked the UI
> and it's still showing the same proxy…
> it's odd, any suggestions?
>
Hmm
One case I could think of is:
if you had two proxies, both of them with the CA functionality, and you
deleted one of them while it was assigned as a CA puppet proxy.
if thats the case (or if you can reproduce) please open a new bug…
thanks!
Ohad
···
On Wed, Sep 5, 2012 at 10:33 AM, Shmiti wrote:
On Wednesday, September 5, 2012 9:55:10 AM UTC+3, ohad wrote:
The proxy IS selected, put the proxy on debug, also put a sniffer on the
proxy server, there is no request arriving to the proxy.
how can I increase the debug in the forman itself?
I have, on both proxies, nothing there.
I think it may be caused since I moved the puppet to another proxy and
there is some inconsistency in the DB?
it seems to me that it’s internal in the forman itself and it can’t
find the right proxy to address to, question is how can I verify that?
you can select the proxy to use per host (just edit the host and
select it).
you can increase the log level to debug in the proxy config
(/etc/foreman-proxy/settings.yml)
Ohad
On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
I had similar problem like Daniel,
I removed the “spoof” from the URL, but now I don’t get the KS file.
foreman says something like:
“Failed to add to autosign file: 404 Resource Not Found”
You should double check the log on your proxy, there is a good chance
you have some sort of permissions error.
the odd part is that in the host configuration, I see
the correct smart proxy (I only have 1 with puppetCA and puppet)
and I do manage to manually add, via foreman, values to the autosign.
On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd > install auto=true priority=critical edd=off
preseed/url=http://xxxx.xxxx.x**xxx/unattended/provision?
spoof******= http://xxxx.xxxx.xxxx/unattended/provision?spoof=<=
ip
%> –
You shouldn’t be using ?spoof for actual installs - its for
checking
the templates are right.
This is working fine as long as i have disabled login.
For my understanding i thought changing it to
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd %> install auto=true priority=critical edd=off
preseed/url=http://xxxx.xxxx.x****xxx/unattended/provisionhttp://xxxx.xxxx.xxxx/unattended/provision–
would solve my problem. But it didn’t …
Sounds like you have a problem with your template generation. This
is
usually related to sudo permissions on the proxy. Check your proxy
logs for any errors when the host requests it’s provision file.
Cheers,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
That was the case.
I can't reproduce it right now as if I enable puppetca in the 1st proxy
now, it still won't show in the UI for some reason.
···
On Wednesday, September 5, 2012 10:36:13 AM UTC+3, ohad wrote:
>
>
>
> On Wed, Sep 5, 2012 at 10:33 AM, Shmiti <el...@shmiti.com >wrote:
>
>> With the debugging I've found that the settings in the host pointed to
>> the wrong proxy, which is odd since in the UI, I couldn't pick a proxy,
>> only 1 is connected to puppetca.
>> I changed the value directly via the DB and it's now ok, checked the UI
>> and it's still showing the same proxy...
>> it's odd, any suggestions?
>>
>
> Hmm
> One case I could think of is:
> if you had two proxies, both of them with the CA functionality, and you
> deleted one of them while it was assigned as a CA puppet proxy.
>
> if thats the case (or if you can reproduce) please open a new bug...
>
> thanks!
> Ohad
>
>>
>> On Wednesday, September 5, 2012 9:55:10 AM UTC+3, ohad wrote:
>>
>>>
>>>
>>> On Wed, Sep 5, 2012 at 9:51 AM, Shmiti wrote:
>>>
>>>> The proxy IS selected, put the proxy on debug, also put a sniffer on
>>>> the proxy server, there is no request arriving to the proxy.
>>>> how can I increase the debug in the forman itself?
>>>>
>>>
>>> see http://theforeman.org/**projects/foreman/wiki/**
>>> Troubleshooting#How-do-I-**enable-debugging
>>> Ohad
>>>
>>>>
>>>> On Wednesday, September 5, 2012 9:46:49 AM UTC+3, ohad wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 5, 2012 at 9:36 AM, Shmiti wrote:
>>>>>
>>>>>> I have, on both proxies, nothing there.
>>>>>> I think it may be caused since I moved the puppet to another proxy
>>>>>> and there is some inconsistency in the DB?
>>>>>> it seems to me that it's internal in the forman itself and it can't
>>>>>> find the right proxy to address to, question is how can I verify that?
>>>>>>
>>>>>
>>>>> 1. you can select the proxy to use per host (just edit the host and
>>>>> select it).
>>>>> 2. you can increase the log level to debug in the proxy config
>>>>> (/etc/foreman-proxy/settings.**y**ml)
>>>>>
>>>>> Ohad
>>>>>
>>>>>>
>>>>>> On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Sep 5, 2012 at 7:55 AM, Shmiti wrote:
>>>>>>>
>>>>>>>> I had similar problem like Daniel,
>>>>>>>> I removed the "spoof" from the URL, but now I don't get the KS file.
>>>>>>>> foreman says something like:
>>>>>>>> "Failed to add to autosign file: 404 Resource Not Found"
>>>>>>>>
>>>>>>>
>>>>>>> You should double check the log on your proxy, there is a good
>>>>>>> chance you have some sort of permissions error.
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> the odd part is that in the host configuration, I see
>>>>>>>> the correct smart proxy (I only have 1 with puppetCA and puppet)
>>>>>>>> and I do manage to manually add, via foreman, values to the
>>>>>>>> autosign.
>>>>>>>>
>>>>>>>> On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
>>>>>>>>>
>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>>>>> Hash: SHA1
>>>>>>>>>
>>>>>>>>> On 29/06/12 10:52, Daniel Verniers wrote:
>>>>>>>>> > Dear ALL,
>>>>>>>>> >
>>>>>>>>> > how was the problem discribed in this post ->
>>>>>>>>> > http://theforeman.org/issues/**1******498solved? My pxe default is
>>>>>>>>> > looking like this
>>>>>>>>> >
>>>>>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>>>>>> > initrd=<= @initrd > install auto=true priority=critical edd=off
>>>>>>>>> > preseed/url=http://xxxx.xxxx.**x******xxx/unattended/provision?*
>>>>>>>>> *spoof******= <=
>>>>>>>>> ip
>>>>>>>>> > %> --
>>>>>>>>>
>>>>>>>>> You shouldn't be using ?spoof for actual installs - its for
>>>>>>>>> checking
>>>>>>>>> the templates are right.
>>>>>>>>>
>>>>>>>>> > This is working fine as long as i have disabled login.
>>>>>>>>> >
>>>>>>>>> > For my understanding i thought changing it to
>>>>>>>>> >
>>>>>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>>>>>> > initrd=<= @initrd %> install auto=true priority=critical edd=off
>>>>>>>>> > preseed/url=http://xxxx.xxxx.**x******xxx/unattended/provision--
>>>>>>>>> >
>>>>>>>>> > would solve my problem. But it didn't ...
>>>>>>>>>
>>>>>>>>> Sounds like you have a problem with your template generation. This
>>>>>>>>> is
>>>>>>>>> usually related to sudo permissions on the proxy. Check your proxy
>>>>>>>>> logs for any errors when the host requests it's provision file.
>>>>>>>>>
>>>>>>>>> Cheers,
>>>>>>>>> Greg
>>>>>>>>> -----BEGIN PGP SIGNATURE-----
>>>>>>>>> Version: GnuPG v2.0.19 (GNU/Linux)
>>>>>>>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>>>>>>>
>>>>>>>>> iEYEARECAAYFAk/**tjmcACgkQ8O7RN8******oK65NwnwCgnhgwB**NQjc/**
>>>>>>>>> zzC6lJIknW****Msv0
>>>>>>>>> /**l0AnApEsAjFcZNQHrV5eOkovp7Qbq******i**t
>>>>>>>>> =p/WN
>>>>>>>>> -----END PGP SIGNATURE-----
>>>>>>>>>
>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "Foreman users" group.
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/d/**ms****g/foreman-users/-/_**
>>>>>>>> hGIDFcVtPQJ
>>>>>>>> ****.
>>>>>>>>
>>>>>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>>>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>>>>>> googlegroups.**c**om.
>>>>>>>>
>>>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>>>> group****/foreman-users?hl=en
>>>>>>>> .
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Foreman users" group.
>>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>>> **ms**g/foreman-users/-/**TiKYEwRiYMQJ
>>>>>> **.
>>>>>>
>>>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>>>> googlegroups.**com.
>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>> group**/foreman-users?hl=en
>>>>>> .
>>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To view this discussion on the web visit https://groups.google.com/d/**
>>>> msg/foreman-users/-/**IvhGNnzJXT8J
>>>> .
>>>>
>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>> googlegroups.com.
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/foreman-users?hl=en
>>>> .
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/foreman-users/-/mICsQksjzb8J.
>>
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> foreman-user...@googlegroups.com .
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
Did you edit and re-save the proxy in the Foreman UI after altering
and restarting the proxy? Foreman doesn't auto-detect those changes,
you have to tell it to re-read the proxy's capabilities.
Greg
···
On 5 September 2012 08:51, Shmiti wrote:
> That was the case.
> I can't reproduce it right now as if I enable puppetca in the 1st proxy now,
> it still won't show in the UI for some reason.
> That was the case.
> I can't reproduce it right now as if I enable puppetca in the 1st proxy
> now, it still won't show in the UI for some reason.
>
great, would you mind opening a bug?
thanks!
···
On Wed, Sep 5, 2012 at 10:51 AM, Shmiti wrote:
On Wednesday, September 5, 2012 10:36:13 AM UTC+3, ohad wrote:
With the debugging I’ve found that the settings in the host pointed to
the wrong proxy, which is odd since in the UI, I couldn’t pick a proxy,
only 1 is connected to puppetca.
I changed the value directly via the DB and it’s now ok, checked the UI
and it’s still showing the same proxy…
it’s odd, any suggestions?
Hmm
One case I could think of is:
if you had two proxies, both of them with the CA functionality, and you
deleted one of them while it was assigned as a CA puppet proxy.
if thats the case (or if you can reproduce) please open a new bug…
thanks!
Ohad
On Wednesday, September 5, 2012 9:55:10 AM UTC+3, ohad wrote:
The proxy IS selected, put the proxy on debug, also put a sniffer on
the proxy server, there is no request arriving to the proxy.
how can I increase the debug in the forman itself?
I have, on both proxies, nothing there.
I think it may be caused since I moved the puppet to another proxy
and there is some inconsistency in the DB?
it seems to me that it’s internal in the forman itself and it can’t
find the right proxy to address to, question is how can I verify that?
you can select the proxy to use per host (just edit the host and
select it).
you can increase the log level to debug in the proxy config
(/etc/foreman-proxy/settings.**y****ml)
Ohad
On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
I had similar problem like Daniel,
I removed the “spoof” from the URL, but now I don’t get the KS
file.
foreman says something like:
“Failed to add to autosign file: 404 Resource Not
Found”
You should double check the log on your proxy, there is a good
chance you have some sort of permissions error.
the odd part is that in the host configuration, I see
the correct smart proxy (I only have 1 with puppetCA and puppet)
and I do manage to manually add, via foreman, values to the
autosign.
On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd > install auto=true priority=critical edd=off
preseed/url=http://xxxx.xxxx.x******
xxx/unattended/provision?spoof******=http://xxxx.xxxx.xxxx/unattended/provision?spoof=<=
ip
%> –
You shouldn’t be using ?spoof for actual installs - its for
checking
the templates are right.
This is working fine as long as i have disabled login.
For my understanding i thought changing it to
default linux label linux kernel <%= @kernel > append vga=788
initrd=<= @initrd %> install auto=true priority=critical
edd=off
preseed/url=http://xxxx.xxxx.x******
xxx/unattended/provisionhttp://xxxx.xxxx.xxxx/unattended/provision–
would solve my problem. But it didn’t …
Sounds like you have a problem with your template generation.
This is
usually related to sudo permissions on the proxy. Check your
proxy
logs for any errors when the host requests it’s provision file.
Cheers,
Greg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
To post to this group, send email to forema...@googlegroups.com**.
To unsubscribe from this group, send email to foreman-user…@**
googlegroups.**c****om.
Done.
Thanks for the quick reply and keep up the great work
···
On Wednesday, September 5, 2012 10:52:06 AM UTC+3, ohad wrote:
>
>
>
> On Wed, Sep 5, 2012 at 10:51 AM, Shmiti <el...@shmiti.com >wrote:
>
>> That was the case.
>> I can't reproduce it right now as if I enable puppetca in the 1st proxy
>> now, it still won't show in the UI for some reason.
>>
> great, would you mind opening a bug?
>
> thanks!
>
>>
>> On Wednesday, September 5, 2012 10:36:13 AM UTC+3, ohad wrote:
>>
>>>
>>>
>>> On Wed, Sep 5, 2012 at 10:33 AM, Shmiti wrote:
>>>
>>>> With the debugging I've found that the settings in the host pointed to
>>>> the wrong proxy, which is odd since in the UI, I couldn't pick a proxy,
>>>> only 1 is connected to puppetca.
>>>> I changed the value directly via the DB and it's now ok, checked the UI
>>>> and it's still showing the same proxy...
>>>> it's odd, any suggestions?
>>>>
>>>
>>> Hmm
>>> One case I could think of is:
>>> if you had two proxies, both of them with the CA functionality, and you
>>> deleted one of them while it was assigned as a CA puppet proxy.
>>>
>>> if thats the case (or if you can reproduce) please open a new bug...
>>>
>>> thanks!
>>> Ohad
>>>
>>>>
>>>> On Wednesday, September 5, 2012 9:55:10 AM UTC+3, ohad wrote:
>>>>
>>>>>
>>>>>
>>>>> On Wed, Sep 5, 2012 at 9:51 AM, Shmiti wrote:
>>>>>
>>>>>> The proxy IS selected, put the proxy on debug, also put a sniffer on
>>>>>> the proxy server, there is no request arriving to the proxy.
>>>>>> how can I increase the debug in the forman itself?
>>>>>>
>>>>>
>>>>> see http://theforeman.org/**project**s/foreman/wiki/**Troubleshooting
>>>>> **#How-do-I-**enable-debugging
>>>>> Ohad
>>>>>
>>>>>>
>>>>>> On Wednesday, September 5, 2012 9:46:49 AM UTC+3, ohad wrote:
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Sep 5, 2012 at 9:36 AM, Shmiti wrote:
>>>>>>>
>>>>>>>> I have, on both proxies, nothing there.
>>>>>>>> I think it may be caused since I moved the puppet to another proxy
>>>>>>>> and there is some inconsistency in the DB?
>>>>>>>> it seems to me that it's internal in the forman itself and it can't
>>>>>>>> find the right proxy to address to, question is how can I verify that?
>>>>>>>>
>>>>>>>
>>>>>>> 1. you can select the proxy to use per host (just edit the host and
>>>>>>> select it).
>>>>>>> 2. you can increase the log level to debug in the proxy config
>>>>>>> (/etc/foreman-proxy/settings.**y****ml)
>>>>>>>
>>>>>>> Ohad
>>>>>>>
>>>>>>>>
>>>>>>>> On Wednesday, September 5, 2012 9:32:39 AM UTC+3, ohad wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On Wed, Sep 5, 2012 at 7:55 AM, Shmiti wrote:
>>>>>>>>>
>>>>>>>>>> I had similar problem like Daniel,
>>>>>>>>>> I removed the "spoof" from the URL, but now I don't get the KS
>>>>>>>>>> file.
>>>>>>>>>> foreman says something like:
>>>>>>>>>> "Failed to add to autosign file: 404 Resource Not
>>>>>>>>>> Found"
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> You should double check the log on your proxy, there is a good
>>>>>>>>> chance you have some sort of permissions error.
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> the odd part is that in the host configuration, I see
>>>>>>>>>> the correct smart proxy (I only have 1 with puppetCA and puppet)
>>>>>>>>>> and I do manage to manually add, via foreman, values to the
>>>>>>>>>> autosign.
>>>>>>>>>>
>>>>>>>>>> On Friday, June 29, 2012 2:15:51 PM UTC+3, Greg Sutcliffe wrote:
>>>>>>>>>>>
>>>>>>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>>>>>>>>> Hash: SHA1
>>>>>>>>>>>
>>>>>>>>>>> On 29/06/12 10:52, Daniel Verniers wrote:
>>>>>>>>>>> > Dear ALL,
>>>>>>>>>>> >
>>>>>>>>>>> > how was the problem discribed in this post ->
>>>>>>>>>>> > http://theforeman.org/issues/**1********498solved? My pxe default is
>>>>>>>>>>> > looking like this
>>>>>>>>>>> >
>>>>>>>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>>>>>>>> > initrd=<= @initrd > install auto=true priority=critical
>>>>>>>>>>> edd=off
>>>>>>>>>>> > preseed/url=http://xxxx.xxxx.**x********
>>>>>>>>>>> xxx/unattended/provision?**spoof********=<=
>>>>>>>>>>> ip
>>>>>>>>>>> > %> --
>>>>>>>>>>>
>>>>>>>>>>> You shouldn't be using ?spoof for actual installs - its for
>>>>>>>>>>> checking
>>>>>>>>>>> the templates are right.
>>>>>>>>>>>
>>>>>>>>>>> > This is working fine as long as i have disabled login.
>>>>>>>>>>> >
>>>>>>>>>>> > For my understanding i thought changing it to
>>>>>>>>>>> >
>>>>>>>>>>> > default linux label linux kernel <%= @kernel > append vga=788
>>>>>>>>>>> > initrd=<= @initrd %> install auto=true priority=critical
>>>>>>>>>>> edd=off
>>>>>>>>>>> > preseed/url=http://xxxx.xxxx.**x********
>>>>>>>>>>> xxx/unattended/provision--
>>>>>>>>>>> >
>>>>>>>>>>> > would solve my problem. But it didn't ...
>>>>>>>>>>>
>>>>>>>>>>> Sounds like you have a problem with your template generation.
>>>>>>>>>>> This is
>>>>>>>>>>> usually related to sudo permissions on the proxy. Check your
>>>>>>>>>>> proxy
>>>>>>>>>>> logs for any errors when the host requests it's provision file.
>>>>>>>>>>>
>>>>>>>>>>> Cheers,
>>>>>>>>>>> Greg
>>>>>>>>>>> -----BEGIN PGP SIGNATURE-----
>>>>>>>>>>> Version: GnuPG v2.0.19 (GNU/Linux)
>>>>>>>>>>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>>>>>>>>>>>
>>>>>>>>>>> iEYEARECAAYFAk/**tjmcACgkQ8O7RN8********oK65NwnwCgnhgwB**NQjc/**
>>>>>>>>>>> zzC6lJIknW******Msv0
>>>>>>>>>>> /**l0AnApEsAjFcZNQHrV5eOkovp7Qbq********i**t
>>>>>>>>>>> =p/WN
>>>>>>>>>>> -----END PGP SIGNATURE-----
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> You received this message because you are subscribed to the
>>>>>>>>>> Google Groups "Foreman users" group.
>>>>>>>>>> To view this discussion on the web visit
>>>>>>>>>> https://groups.google.com/d/**ms******g/foreman-users/-/_**
>>>>>>>>>> hGIDFcVtPQJ
>>>>>>>>>> ******.
>>>>>>>>>>
>>>>>>>>>> To post to this group, send email to forema...@googlegroups.com**
>>>>>>>>>> .
>>>>>>>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>>>>>>>> googlegroups.**c****om.
>>>>>>>>>>
>>>>>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>>>>>> group******/foreman-users?hl=en
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>> You received this message because you are subscribed to the Google
>>>>>>>> Groups "Foreman users" group.
>>>>>>>> To view this discussion on the web visit
>>>>>>>> https://groups.google.com/d/**ms****g/foreman-users/-/**
>>>>>>>> TiKYEwRiYMQJ
>>>>>>>> ****.
>>>>>>>>
>>>>>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>>>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>>>>>> googlegroups.**c**om.
>>>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>>>> group****/foreman-users?hl=en
>>>>>>>> .
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "Foreman users" group.
>>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>>> **ms**g/foreman-users/-/**IvhGNnzJXT8J
>>>>>> **.
>>>>>>
>>>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>>>> googlegroups.**com.
>>>>>> For more options, visit this group at http://groups.google.com/**
>>>>>> group**/foreman-users?hl=en
>>>>>> .
>>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Foreman users" group.
>>>> To view this discussion on the web visit https://groups.google.com/d/**
>>>> msg/foreman-users/-/**mICsQksjzb8J
>>>> .
>>>>
>>>> To post to this group, send email to forema...@googlegroups.com**.
>>>> To unsubscribe from this group, send email to foreman-user...@**
>>>> googlegroups.com.
>>>> For more options, visit this group at http://groups.google.com/**
>>>> group/foreman-users?hl=en
>>>> .
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msg/foreman-users/-/0jL18LNNLp0J.
>>
>> To post to this group, send email to forema...@googlegroups.com
>> .
>> To unsubscribe from this group, send email to
>> foreman-user...@googlegroups.com .
>> For more options, visit this group at
>> http://groups.google.com/group/foreman-users?hl=en.
>>
>
>
