On 13/10/16 21:24, Mike Wilson wrote:
> Here is where I have the problem, with host4a. The puppet runs complain:
> |
> Error: Could not retrieve catalog from remote server: Error 500 on
> SERVER: {"message":"Server Error: Could not find class motd for
> host4a.name.com on node
> host4a.name.com", [..]

The error indicates that Foreman is specifying the "motd" module must be
applied, but it isn't on the Puppet master. It's likely that it's in the
wrong location, or a setting such as the environmentpath in puppet.conf
is incorrect.

> I also have reviewed the smart proxy/class/host group settings trying to
> see if there is something I left out from the new host4/host4a since the
> only difference from these and the ones that work are it is on a
> different compute resource... but didn't see anything obvious.

Assuming the environments are meant to be identical, I don't think this
is related at all to Foreman.

> Anyone have suggestions on where I might look at this for a cause?

If you show the exact locations of the modules, manifests and
puppet.conf (plus version), it might be possible to say what the issue is.

Dominic Cleal

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.

Reply via email to