types and even class not being found sometimes.

[Steve Traylen]

Hi,

 Today we updated puppet-2.7.14-1 to -2 which should have been boring.

  I am sure the update is not significant and I did it with out thinking about it.

  Its probably that this just caused a restart everywhere.

  I was sure I read a bug about custom defined types not being found sometimes but I have

  been unable to find it just now?

  Since this morning:

  err: Could not retrieve catalog from remote server: Error 400 on SERVER: Cannot find definition Lemon::Metric at /etc/puppet/environments/master/modules/lemon/manifests/standard.pp:53 on node lxfssm4308.cern.ch

 though this is not a consistent error , the compilation works most of the time and  

  

  /etc/puppet/environments/master/modules/lemon/manifests/metric.pp

  containing: 

  define lemon::metric(..) { ...

  The situation is not restricted to custom metrics and also sometimes 'class' itself is not defined.

  Could not retrieve catalog from remote server: Error 400 on SERVER: Cannot find definition Class on node lbdai02.cern.ch

  Puppet master is RHEL6 with puppetlabs puppet packages.

I tried producing a debug or trace log but under with these the types are found.

Steve.

  

 

[Moses Mendoza]

Hi Steven,

Just to clarify, the 2.7.14-1 to -2 release was a packaging change, which made puppet depend on facter >= 1.5 and < 2.0, instead of just >= 1.5 as it was before. This change is to prevent puppet installs from pulling in facter 2.0 when it is placed in the puppet labs yum/apt product repos after going to production release, and will be carried forward on the 2.7.x branch. It shouldn't have any effect puppet's behavior. Maybe some other changes occurred?

Moses

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

[Steve Traylen]

On Friday, 8 June 2012 01:10:54 UTC+2, Moses Mendoza wrote:

Hi Steven,

Just to clarify, the 2.7.14-1 to -2 release was a packaging change, which made puppet depend on facter >= 1.5 and < 2.0, instead of just >= 1.5 as it was before. This change is to prevent puppet installs from pulling in facter 2.0 when it is placed in the puppet labs yum/apt product repos after going to production release, and will be carried forward on the 2.7.x branch. It shouldn't have any effect puppet's behavior. Maybe some other changes occurred?

yes understood, As I said the upgrade caused a restart but not anything else. I also did a rpmdev-diff the two packages just

to check something  accidental had not happened. They are as  you say identical beyond the meta data. 

an aside: I guess you did this because facter2.0.0rc2 was released by accident... best solution in this case is epoch bump the facter 1, package.

On Thu, Jun 7, 2012 at 3:38 PM, Steve Traylen <steve....@cern.ch> wrote:

Hi,

 Today we updated puppet-2.7.14-1 to -2 which should have been boring.

  I am sure the update is not significant and I did it with out thinking about it.

  Its probably that this just caused a restart everywhere.

  I was sure I read a bug about custom defined types not being found sometimes but I have

  been unable to find it just now?

  Since this morning:

  err: Could not retrieve catalog from remote server: Error 400 on SERVER: Cannot find definition Lemon::Metric at /etc/puppet/environments/master/modules/lemon/manifests/standard.pp:53 on node lxfssm4308.cern.ch

 though this is not a consistent error , the compilation works most of the time and  

  

  /etc/puppet/environments/master/modules/lemon/manifests/metric.pp

  containing: 

  define lemon::metric(..) { ...

  The situation is not restricted to custom metrics and also sometimes 'class' itself is not defined.

  Could not retrieve catalog from remote server: Error 400 on SERVER: Cannot find definition Class on node lbdai02.cern.ch

  Puppet master is RHEL6 with puppetlabs puppet packages.

I tried producing a debug or trace log but under with these the types are found.

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/-/u3HzsLPt6awJ.
To post to this group, send email to puppet...@googlegroups.com.

To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com.

[Moses Mendoza]

On Jun 7, 2012, at 4:19 PM, Steve Traylen <steve....@cern.ch> wrote:

On Friday, 8 June 2012 01:10:54 UTC+2, Moses Mendoza wrote:

Hi Steven,

Just to clarify, the 2.7.14-1 to -2 release was a packaging change, which made puppet depend on facter >= 1.5 and < 2.0, instead of just >= 1.5 as it was before. This change is to prevent puppet installs from pulling in facter 2.0 when it is placed in the puppet labs yum/apt product repos after going to production release, and will be carried forward on the 2.7.x branch. It shouldn't have any effect puppet's behavior. Maybe some other changes occurred?

yes understood, As I said the upgrade caused a restart but not anything else. I also did a rpmdev-diff the two packages just

to check something  accidental had not happened. They are as  you say identical beyond the meta data. 

an aside: I guess you did this because facter2.0.0rc2 was released by accident... best solution in this case is epoch bump the facter 1, package.

Yes, and also because Facter 2.0 is not backwards compatible with 2.6.x and 2.7.x. When 2.0 goes production, we want to make sure it doesn't get pulled in with current/forthcoming releases of 2.7.x. The epoch idea is great as well, and I'll likely roll it out tomorrow.

On Thu, Jun 7, 2012 at 3:38 PM, Steve Traylen <steve....@cern.ch> wrote:

Hi,

 Today we updated puppet-2.7.14-1 to -2 which should have been boring.

  I am sure the update is not significant and I did it with out thinking about it.

  Its probably that this just caused a restart everywhere.

  I was sure I read a bug about custom defined types not being found sometimes but I have

  been unable to find it just now?

  Since this morning:

  err: Could not retrieve catalog from remote server: Error 400 on SERVER: Cannot find definition Lemon::Metric at /etc/puppet/environments/master/modules/lemon/manifests/standard.pp:53 on node lxfssm4308.cern.ch

 though this is not a consistent error , the compilation works most of the time and  

  

  /etc/puppet/environments/master/modules/lemon/manifests/metric.pp

  containing: 

  define lemon::metric(..) { ...

  The situation is not restricted to custom metrics and also sometimes 'class' itself is not defined.

  Could not retrieve catalog from remote server: Error 400 on SERVER: Cannot find definition Class on node lbdai02.cern.ch

  Puppet master is RHEL6 with puppetlabs puppet packages.

I tried producing a debug or trace log but under with these the types are found.

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

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

To post to this group, send email to puppet...@googlegroups.com.

To unsubscribe from this group, send email to puppet-users...@googlegroups.com.

[Felix Frank]

Hi,

On 06/08/2012 12:38 AM, Steve Traylen wrote:
> err: Could not retrieve catalog from remote server: Error 400 on
> SERVER: Cannot find definition Lemon::Metric at
> /etc/puppet/environments/master/modules/lemon/manifests/standard.pp:53
> on node lxfssm4308.cern.ch

I get the pretty often during a run immediately following one against a
broken manifest with syntax errors. The compiler bailed out of the
manifest earlier and somehow the master's cache can be confused by that
- or something?

Rerunning consistently fixes this. Could you be facing a similar situation?

Cheers,
Felix

[Steve Traylen]

Solved but confusing. I have 

[main]

modulepath = /etc/puppet/modules

manifest   = /etc/puppet/modules/site.pp

[production]

modulepath = /etc/puppet/environments/master/modules

manifest   = /etc/puppet/environments/master/site.pp

That last site.pp was completely missing, the first site.pp was empty. (An enc is in use)

I'm happy this its okay after creating the second site.pp but its not obvious why this

would be a "sometimes" error.

Steve.

 

Cheers,
Felix