Re: [Puppet Users] Storeconfigs: facts not updated

2011-03-04 Thread Martijn Grendelman
After completely deleting the node from the database's 'host' table and
resources that referenced its host_id, a following catalog run refreshed
the database, adding all facts with their current values...

Best regards,
Martijn.


On 04-03-11 12:43, Martijn Grendelman wrote:
> Hi,
> 
> I run the Puppetmaster with
> 
> storeconfigs = true
> thin_storeconfigs = true
> dbadapter = mysql
> 
> So far, this has been working perfectly, but today I noticed something
> odd. Yesterday, I upgraded one of my nodes from Ubuntu Jaunty to Lucid,
> but the facts from this node aren't updated in the database.
> 
> For example, the database still said (and notice the timestamps, they are
> current!):
> 
> 2011-03-04 11:39:05 kernelrelease 2.6.28-17-server
> 2011-03-04 11:39:05 lsbdistcodename   jaunty
> 2011-03-04 11:39:05 lsbdistdescriptionUbuntu 9.04
> 
> While 'facter' on the machine itself correctly reports:
> 
> kernelrelease => 2.6.32-29-generic-pae
> lsbdistcodename => lucid
> lsbdistdescription => Ubuntu 10.04.2 LTS
> 
> Then I thought I'd just remove all the facts from the database, to have
> Puppet refresh them, so I did "delete FROM `fact_values` where host_id=27".
> 
> On the next Puppet run, I got:
> 
> err: Could not retrieve catalog from remote server: Error 400 on SERVER:
> No matching value for selector param 'undef' at
> /etc/puppet/manifests/site.pp:37 on node abcxyz.
> 
> This error refers to a selector that uses the fact $operatingsystem, which
> now appears to be 'undef'.
> 
> Now, if I completely disable storeconfigs on the master, a Puppet run
> succeeds like ever before, but as soon as storeconfigs is re-enabled, the
> 'undef' error returns.
> 
> What could be the cause of this?
> 
> One thing possibly worth mentioning: this node runs the Puppetmaster. No
> idea if that makes a difference. Everything is version 2.6.3.
> 
> Regards,
> Martijn.
> 

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



[Puppet Users] Storeconfigs: facts not updated

2011-03-04 Thread Martijn Grendelman
Hi,

I run the Puppetmaster with

storeconfigs = true
thin_storeconfigs = true
dbadapter = mysql

So far, this has been working perfectly, but today I noticed something
odd. Yesterday, I upgraded one of my nodes from Ubuntu Jaunty to Lucid,
but the facts from this node aren't updated in the database.

For example, the database still said (and notice the timestamps, they are
current!):

2011-03-04 11:39:05 kernelrelease   2.6.28-17-server
2011-03-04 11:39:05 lsbdistcodename jaunty
2011-03-04 11:39:05 lsbdistdescription  Ubuntu 9.04

While 'facter' on the machine itself correctly reports:

kernelrelease => 2.6.32-29-generic-pae
lsbdistcodename => lucid
lsbdistdescription => Ubuntu 10.04.2 LTS

Then I thought I'd just remove all the facts from the database, to have
Puppet refresh them, so I did "delete FROM `fact_values` where host_id=27".

On the next Puppet run, I got:

err: Could not retrieve catalog from remote server: Error 400 on SERVER:
No matching value for selector param 'undef' at
/etc/puppet/manifests/site.pp:37 on node abcxyz.

This error refers to a selector that uses the fact $operatingsystem, which
now appears to be 'undef'.

Now, if I completely disable storeconfigs on the master, a Puppet run
succeeds like ever before, but as soon as storeconfigs is re-enabled, the
'undef' error returns.

What could be the cause of this?

One thing possibly worth mentioning: this node runs the Puppetmaster. No
idea if that makes a difference. Everything is version 2.6.3.

Regards,
Martijn.

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