When I have foreman::oauth_active set to false, install attempts result in
the following error:
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman2.domain]:
Could not evaluate: Proxy foreman2.domain cannot be retrieved: unknown
error (response 401)
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:7:in proxy' /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:13:inid'
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:17:in exists?' /usr/share/ruby/vendor_ruby/puppet/property/ensure.rb:81:inretrieve'
etc.
The httpd error log shows the 401 error as well, mentioning "OAuth gem
v0.4.7" at the end of the line - which was surprising considering I thought
I'd set oauth_active to false.
When I enable oauth (which I do not actually want to do), the installer
runs great.
> When I have foreman::oauth_active set to false, install attempts result
> in the following error:
>
> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman2.domain]: Could
> not evaluate: Proxy foreman2.domain cannot be retrieved: unknown error
> (response 401)
> /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:7:in
> proxy' > /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:13:in >id'
> /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:17:in
> exists?' > /usr/share/ruby/vendor_ruby/puppet/property/ensure.rb:81:inretrieve'
> etc.
>
> The httpd error log shows the 401 error as well, mentioning "OAuth gem
> v0.4.7" at the end of the line - which was surprising considering I
> thought I'd set oauth_active to false.
Automatic registration of the smart proxy from the installer requires
OAuth, it uses it to authenticate to Foreman.
> When I enable oauth (which I do not actually want to do), the installer
> runs great.
>
> Can anyone tell me what I'm missing here?
You will need to disable registration
(–foreman-proxy-register-in-foreman=false) and then add the smart proxy
manually via the UI or CLI.
···
On 19/10/16 00:04, cjacobs@rentrakmail.com wrote:
I've dug around the hammer interface and this seems to be the only thing
that matches (to my inexperience in foreman/hammer eyes).
Thanks,
chris
···
On Wednesday, October 19, 2016 at 12:17:18 AM UTC-7, Dominic Cleal wrote:
>
> On 19/10/16 00:04, cja...@rentrakmail.com wrote:
> > When I have foreman::oauth_active set to false, install attempts result
> > in the following error:
> >
> >
> /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[foreman2.domain]:
> Could
> > not evaluate: Proxy foreman2.domain cannot be retrieved: unknown error
> > (response 401)
> >
> /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:7:in
>
> > `proxy'
> >
> /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:13:in
>
> > `id'
> >
> /usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:17:in
>
> > `exists?'
> > /usr/share/ruby/vendor_ruby/puppet/property/ensure.rb:81:in `retrieve'
> > etc.
> >
> > The httpd error log shows the 401 error as well, mentioning "OAuth gem
> > v0.4.7" at the end of the line - which was surprising considering I
> > thought I'd set oauth_active to false.
>
> Automatic registration of the smart proxy from the installer requires
> OAuth, it uses it to authenticate to Foreman.
>
> > When I enable oauth (which I do not actually want to do), the installer
> > runs great.
> >
> > Can anyone tell me what I'm missing here?
>
> You will need to disable registration
> (--foreman-proxy-register-in-foreman=false) and then add the smart proxy
> manually via the UI or CLI.
>
> --
> Dominic Cleal
> dom...@cleal.org
>
Yes, that's correct. The refresh-features is probably redundant, it
should update when first created.
···
On 28/10/16 20:36, cjacobs@rentrakmail.com wrote:
> Does this perform the registration (and likely redundant refresh):
>
> hammer proxy create --name $HOSTNAME --url https://$HOSTNAME:8443
> hammer proxy refresh-features --name $HOSTNAME
>
> I've dug around the hammer interface and this seems to be the only thing
> that matches (to my inexperience in foreman/hammer eyes).
