Re: trouble with catalog with Foreman as ENC

[confused]

Nothing?  I'm able to reproduce this problem without using Foreman.  If I add a new class to a host in Puppet's site.pp, I still get 'Could not retrieve catalog from remote server: Error 400 on SERVER' message.

Would really appreciate any pointers on troubleshooting this problem.  My existing classes are working and I can edit them and have the updates work.  I am not able to add any new classes to my hosts without the client getting a 400 error.

[R.I.Pienaar]

----- Original Message -----
> From: "confused" <sboy...@gmail.com>
> To: puppet...@googlegroups.com
> Sent: Tuesday, September 4, 2012 5:51:57 PM
> Subject: [Puppet Users] Re: trouble with catalog with Foreman as ENC
>
>
> Nothing? I'm able to reproduce this problem without using Foreman. If
> I add a new class to a host in Puppet's site.pp, I still get 'Could
> not retrieve catalog from remote server: Error 400 on SERVER'
> message.
>

The error is "Could not find class connexityApt", this means it cant find
your puppet class.

The documentation[1] states class names has to be all lowercase


[1] http://docs.puppetlabs.com/puppet/2.7/reference/lang_reserved.html

[confused]

Thank you, that was very helpful.  

Now I need to work through:

err: /Stage[main]/Connexity_apt/File[/etc/apt/sources.list.d/connexity.list]: Could not evaluate: getaddrinfo: Name or service not known Could not retrieve file metadata for puppet://modules/connexity_apt/connexity.list: getaddrinfo: Name or service not known at /opt/puppet/modules/connexity_apt/manifests/init.pp:6

Or this:

err: /Stage[main]/Connexity_apt/File[/etc/apt/sources.list.d/connexity.list]: Could not evaluate: Error 400 on SERVER: Not authorized to call find on /file_metadata/puppet/modules/connexity_apt/etc/apt/sources.list.d/connexity.list Could not retrieve file metadata for puppet:///puppet/modules/connexity_apt/etc/apt/sources.list.d/connexity.list: Error 400 on SERVER: Not authorized to call find on /file_metadata/puppet/modules/connexity_apt/etc/apt/sources.list.d/connexity.list at /opt/puppet/modules/connexity_apt/manifests/init.pp:6

I'm sure that I'm missing something simple here again, apparently I'm on the steep part of the learning curve.

 

[Sam Kottler]

That means that modules/connexity_apt/files/connexity.list doesn't exist.

-Sam

 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ptkwXpwGGvYJ.

To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

[confused]

Got it, thanks.  I appreciate the assistance.

[Erik Dalén]

Actually I think the problem is that the source parameter should begin
with puppet:/// (3 slashes), otherwise it will tro to look up the
server "modules" and that failed.

--
Erik Dalén