[foreman-users] Re: Updating puppet from 3.8.7 to 4.8.1 with Foreman 1.12.4 on EL6.8.

2017-08-15 Thread darsh
After Updating puppet server from 3.8.7 to 4.10 on Foreman 1.15.1.
I am getting the same error messages as you did on client machines, 'Error: 
Could not retrieve catalog from remote server: Error 500 on SERVER...'

I 
followed 
http://projects.theforeman.org/projects/foreman/wiki/Upgrading_from_Puppet_3_to_4

My puppet.conf has vardir = /opt/puppetlabs/puppet/cache

And I copied /var/lib/puppet/foreman_cache_data to 
/opt/puppetlabs/puppet/cache/foreman_cache_data

You said, 'I fixed this by setting the correct puppet cache directory for 
foreman'. Can you please let me know what exactly you did?

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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


[foreman-users] Re: Updating puppet from 3.8.7 to 4.8.1 with Foreman 1.12.4 on EL6.8.

2016-12-02 Thread jp10558
I fixed this by setting the correct puppet cache directory for foreman. Now 
I'm on to another issue, where I cannot import puppet classes because of:

ERF12-4115  406 Not Acceptable ... We've tried changing the auth.conf rules 
to no effect - that shows me a wiki page that has me check 
/var/log/foreman-proxy/proxy.log
which shows:
ERROR -- : Failed to show puppet classes: 403 {"message":"Not Authorized: 
Forbidden request: /puppet/v3/resource_type/* 
[search]","issue_kind":"RUNTIME_ERROR"}

The fix for this ended up being disabling the legacy auth.conf and just 
using the new format with the suggested foreman settings from their guide. 
V3 agents check in successfully. 

Final take away - I think that anyone else trying this after us should 
mostly follow the foreman wiki and ignore a lot of the server / master 
stuff from puppet directly. Of course you do need to refer to puppet 
guidelines for fixing the manifests. Future parser did not find a lot of 
issues for us so we ended up fixing them after the upgrade - carefully 
working through the puppet guidelines and not assuming the agents will 
error would also help.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.