Puppet users - Nov 2011 - Intermittent Error 400 catalog failure

I have one host, the only one using this class, where it occasionally gets
the following error.  I''d guess this happens 1/3 of the time, but seems
to
work for several runs, then fail for several runs.

Could not retrieve catalog from remote server: Error 400 on SERVER: Could
not find class server::e1 for e1.xxx.xxx on node e1.xxx.xxx

This started when we installed 2.7.5, upgrading from 2.6.8 or .9.  Foreman
0.3 is also in use, but to me, this doesn''t look like foreman.  I also
upgraded the client to 2.7.6 but it didn''t change the symptoms.

Any thoughts?

-- 
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.

Len,

I would be very interested in the details of your Puppet Master system
running 2.7.5.  Any configs you are willing to share would be appreciated.
Also, it would be most helpful if you can reproduce one of the failed runs
using from a Puppet client using:

puppet agent --test --debug

Thanks!

On Tue, Nov 1, 2011 at 6:27 AM, Len Rugen <lenrugen@gmail.com> wrote:
> I have one host, the only one using this class, where it occasionally gets
> the following error.  I''d guess this happens 1/3 of the time, but
seems to
> work for several runs, then fail for several runs.
>
> Could not retrieve catalog from remote server: Error 400 on SERVER: Could
> not find class server::e1 for e1.xxx.xxx on node e1.xxx.xxx
>
> This started when we installed 2.7.5, upgrading from 2.6.8 or .9.  Foreman
> 0.3 is also in use, but to me, this doesn''t look like foreman.  I
also
> upgraded the client to 2.7.6 but it didn''t change the symptoms.
>
> Any thoughts?
>
>  --
> 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.
>


-- 
Dominic Maraglia
QA Engineer
Puppet Labs

-- 
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.

On Tue, Nov 1, 2011 at 6:27 AM, Len Rugen <lenrugen@gmail.com> wrote:
> I have one host, the only one using this class, where it occasionally gets
> the following error.  I''d guess this happens 1/3 of the time, but
seems to
> work for several runs, then fail for several runs.
>
> Could not retrieve catalog from remote server: Error 400 on SERVER: Could
> not find class server::e1 for e1.xxx.xxx on node e1.xxx.xxx
>
> This started when we installed 2.7.5, upgrading from 2.6.8 or .9.  Foreman
> 0.3 is also in use, but to me, this doesn''t look like foreman.  I
also
> upgraded the client to 2.7.6 but it didn''t change the symptoms.
>
A change from 2.6 to 2.7 was that ENC-specified classes now fail if they
can''t be found, just like classes that you''ve included via
manifests.

-- 
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.

It could be this issue if you are using imports in your Puppet code.

https://projects.puppetlabs.com/issues/8433

-- 
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.

Yes, this fits.  I''ll change my structure and see if it goes away. 
(Still,
would it work sometimes but not always?)

On Tue, Nov 1, 2011 at 2:55 PM, Chuck <csschwe@gmail.com> wrote:
> It could be this issue if you are using imports in your Puppet code.
>
> https://projects.puppetlabs.com/issues/8433
>
> --
> 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.
>
>
-- 
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.