Upgraded from Satellite 6.2.11 to 6.3.5 Puppet 4 now have 2issues

Latest response

So I followed all the steps from here https://access.redhat.com/documentation/en-us/red_hat_satellite/6.3/html-single/upgrading_and_updating_red_hat_satellite/#upgrading_puppet-1
To upgrade everything updated no issues.
Puppet updated no issues.
Issue 1
Now all my hosts are in error under Content Hosts-> (the host) Provisioning -> Provisioning Details.
When I run the steps for puppet on the Content host I get the below error.
Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Evaluation Error: Comparison of: String < Integer, is not possible. Caused by 'A String is not comparable to a non String'. at /etc/puppetlabs/code/environments/KT_QA_PuppetForge_3/modules/nfs/manifests/client/rhel/packages.pp:9:37 on node damp01
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run

Issue 2
If I go to look at a template to provision I get the following error. This I am hoping can get resolved quickly as I have a few servers to provision soon
There was an error rendering the Satellite Kickstart Default - Custom template: Safemode doesn't allow to access 'block_pass' on &:present?

Thanks in advance. I am hoping to solve here before logging ticket.

Responses

Hi James,

I'll start by saying I didn't specifically have that error and I don't have any puppet config. I just had problems with my provisioning templates.

I'm not sure which version it was but after a recent upgrade to Satellite (have gone 6.2 > 6.3 and 6.3 > 6.4) had issues with my customised provisioning templates. Turned out the default templates were changed (the old standard templates were marked as deprecated) and so I had to re-clone and recreate my custom templates from the new provisioning templates for the newer version of Satellite.

Regards, Peter

Thanks Peter appreciate the feedback. I also figured out my puppet issue. had a puppet module that was notated as valid for Puppet 4 but wasn't so was causing the errors.