Puppet users - Aug 2012 - trouble with catalog with Foreman as ENC

I''m running the following:
Puppet Version 2.7.11
Foreman Version 1.0.1
Ruby 1.8.7
activemodel (3.0.11)
activerecord (3.0.11)
activesupport (3.0.11)
arel (2.0.10)
builder (2.1.2)
i18n (0.5.0)
kgio (2.7.4)
pg (0.14.0)
rack (1.4.1)
raindrops (0.10.0)
tzinfo (0.3.33)
unicorn (4.3.1)

I have the puppetmaster and Foreman running under unicorn with nginx as a 
proxy, which seems to work fine.  I''m having trouble when I assign a
class
to a node.

I have some existing classes that are working, I can get the yaml from 
Foreman and Puppet complete as expected:
http://pastebin.com/i2G5UkFr

Then I add a new class to that host, I can get the updated yaml from 
Foreman but Puppet fails with Could not retrieve catalog from remote 
server: Error 400 on SERVER:
http://pastebin.com/a0YdTCw3

I can test the module directly on the puppetmaster host and it seems to 
work:
http://pastebin.com/7SAHAyRM

Any suggestions are greatly appreciated.

Thanks,
Steve

-- 
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/-/91Lr2_xgtaEJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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.

-- 
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/-/PF-IDjQNwFUJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

----- Original Message -----
> From: "confused" <sboyle.sb@gmail.com>
> To: puppet-users@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

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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.


 

-- 
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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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

-Sam

On Tue, Sep 4, 2012 at 2:01 PM, confused <sboyle.sb@gmail.com> wrote:
> 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.
>
>
>
>
> --
> 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-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

Got it, thanks.  I appreciate the assistance.
>
>
-- 
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/-/Byoko1rC37QJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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.

On 4 September 2012 20:12, Sam Kottler <sam@kottlerdevelopment.com>
wrote:
> That means that modules/connexity_apt/files/connexity.list doesn''t
exist.
>
> -Sam
>
> On Tue, Sep 4, 2012 at 2:01 PM, confused <sboyle.sb@gmail.com> wrote:
>>
>> 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.
>>
>>
>>
>>
>> --
>> 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-users@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.


-- 
Erik Dalén

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.