Foreman proxy (foreman 1.3) registration error

Support
1

Hi,

I just upgraded my foreman to 1.3, and I face a strange error :

Error: Could not set 'present' on ensure: 422 Unprocessable Entity at 12:/etc/puppet/envs/dev/puppet/foreman_proxy/manifests/register.pp
/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in return!' /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:230:inprocess_result'
/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:178:in transmit' /usr/lib/ruby/1.8/net/http.rb:543:instart'
/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in transmit' /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:64:inexecute'
/usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in execute' /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/resource.rb:71:inpost'
/usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/base.rb:77:in send' /usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/base.rb:77:inhttp_call'
/usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/base.rb:60:in perform_call' /usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/resources/smart_proxy.rb:37:increate'
/etc/puppet/envs/dev/puppet/foreman/lib/puppet/provider/foreman_smartproxy/rest.rb:31:in create' /usr/lib/ruby/site_ruby/1.8/puppet/property/ensure.rb:16:inset_present'

The foreman server is up and running and displaying the 1.3 UI.
When looking at the production.log, I see :

Started POST "/api/smart_proxies" for xxx0 at 2013-10-15 12:24:58 +0200
Processing by Api::V1::SmartProxiesController#create as JSON
Parameters: {"smart_proxy"=>{"url"=>"https://xxx:8443", "name"=>"xxx"}}
Authorized user admin(Admin User)
Unprocessable entity SmartProxy (id: new):
URL Only one declaration of a proxy is allowed

I had done a 1.1 -> 1.3 upgrade on a test VM, with the same db, and did not face that (or did not notice it).
Any idea on how that could be fixed ?

This is the puppetmaster configuring itself with the 1.3RC4 installer modules (I did not check if there was a change between the RC4 and the release… is that my mistake ?)

Thanks

2

Hello,

the thing is our installer now tries to deploy proxy entry with name of
the proxy hostname and valid URL.

If you have existing entry there with the same URL but under different
name, you have two opinions:

a) Turn off proxy registration in puppet (you can do this in the
foreman-installer option - see --help)

b) Rename that existing proxy so it's name is the hostname of the proxy.
E.g.:

name: my.proxy.org
url: https://my.proxy.org:8443

They must be same.

LZ

··· On Tue, Oct 15, 2013 at 10:41:17AM +0000, SCHAER Frederic wrote: > Hi, > > I just upgraded my foreman to 1.3, and I face a strange error : > > Error: Could not set 'present' on ensure: 422 Unprocessable Entity at 12:/etc/puppet/envs/dev/puppet/foreman_proxy/manifests/register.pp > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/abstract_response.rb:48:in `return!' > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:230:in `process_result' > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:178:in `transmit' > /usr/lib/ruby/1.8/net/http.rb:543:in `start' > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:172:in `transmit' > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:64:in `execute' > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/request.rb:33:in `execute' > /usr/lib/ruby/gems/1.8/gems/rest-client-1.6.7/lib/restclient/resource.rb:71:in `post' > /usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/base.rb:77:in `send' > /usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/base.rb:77:in `http_call' > /usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/base.rb:60:in `perform_call' > /usr/lib/ruby/gems/1.8/gems/foreman_api-0.1.6/lib/foreman_api/resources/smart_proxy.rb:37:in `create' > /etc/puppet/envs/dev/puppet/foreman/lib/puppet/provider/foreman_smartproxy/rest.rb:31:in `create' > /usr/lib/ruby/site_ruby/1.8/puppet/property/ensure.rb:16:in `set_present' > > The foreman server is up and running and displaying the 1.3 UI. > When looking at the production.log, I see : > > Started POST "/api/smart_proxies" for xxx0 at 2013-10-15 12:24:58 +0200 > Processing by Api::V1::SmartProxiesController#create as JSON > Parameters: {"smart_proxy"=>{"url"=>"https://xxx:8443", "name"=>"xxx"}} > Authorized user admin(Admin User) > Unprocessable entity SmartProxy (id: new): > URL Only one declaration of a proxy is allowed > > > I had done a 1.1 -> 1.3 upgrade on a test VM, with the same db, and did not face that (or did not notice it). > Any idea on how that could be fixed ? > > This is the puppetmaster configuring itself with the 1.3RC4 installer modules (I did not check if there was a change between the RC4 and the release... is that my mistake ?) > > Thanks > > -- > 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/groups/opt_out.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman