Bug #1884

Exported resources are marked as unexported when collected on the exporting host

Added by Eric Eisenhart about 3 years ago. Updated almost 2 years ago.

Status:Closed Start date:01/22/2009
Priority:Normal Due date:
Assignee:James Turnbull % Done:

0%
Category:plumbing
Target version:0.24.8
Affected Puppet version:0.24.7 Branch:
Keywords:
Votes: 0

Description

@@host { $foo: ip => $bar, ensure => present } Host <<| |>> @@sshkey { $foo: type => rsa, key => $sshrsakey } Sshkey <<| |>>

[puppetmasterd] storeconfigs=true dbadapter=mysql (etc)

This was working before. I think in 0.24.4, but possibly 0.24.3 or 0.24.2…

When I added a new node, those resources appeared on that new node, but never appeared on other nodes. Older exported resources worked on the new node.

In the “resources” table in mysql the exported column was NULL.

Manually changing the exported column to 1 for the affected resources seemed to work around the problem.

History

#1
Updated by James Turnbull about 3 years ago

  • Category set to plumbing
  • Status changed from Unreviewed to Accepted

#2
Updated by Andrew Shafer about 3 years ago

I have the head of 0.24.x and exporting seems to be working.

I’m using sqlite3, and I hope to hell that should be fine.

I’ll go back through the tags and see if I can find a problem.

And maybe freiheit can help me reproduce?

#3
Updated by Tim Stoop about 3 years ago

We’re experiencing this too in a new setup. In MySQL, the ‘exported’ value in the table ‘resources’ is NULL. When we manually set it to 1, the resources get exported and collected. This is on Debian Etch with 0.24.7 from a home-made package, but no patches were applied to the puppet source.

I’ll try to see if I can reproduce this in a VM, will get back to you about that.

Oh, problem seems to be something on the host, because it won’t work in 0.24.5 either.

#4
Updated by Tim Stoop about 3 years ago

Ok, I have a Parallels Desktop VM that experiences this behaviour. I’m uploading the VM as I write this, should be available at http://tim.hokkertjes.nl/puppet-1884.tar.bz2 about 90 minutes after I write this comment.

Details about the VM: – Debian Etch – Backported packages from testing: rails and libbuilder-ruby1.8 – Puppet 0.24.5 (but it’s exactly the same behaviour with 0.24.7)

Using the VM: – login: tim – password: puppet – MySQL credentials in /etc/puppet/puppet.conf – Manifest in /etc/puppet/manifests/site.pp – Check out the resources table in MySQL to see multiple sshkey exported resource which have the exported field set to NULL – rm /etc/ssh/ssh_know_hosts – sudo /etc/init.d/puppet restart; tail -f /var/log/daemon (ignore the fileserver errors)

You’ll see that only the own hostname is changed.

To test further, edit /etc/hostname and change it into something else. Reboot the VM. Try again. All data from the previous run should still be in the database.

The packages out of the kumina repository (http://debian.kumina.nl) are simply backported packages from Lenny to Etch.

#5
Updated by Luke Kanies about 3 years ago

  • Subject changed from resource export with mysql stopped working. to Exported resources are marked as unexported when collected on the exporting host
  • Target version changed from 0.25.0 to 0.24.8

#6
Updated by Luke Kanies about 3 years ago

  • Status changed from Accepted to Ready For Checkin
  • Assignee set to James Turnbull

Fixed in my tickets/0.24.x/1884 repo. Note that this will probably have a simple merge conflict with Brice’s fix for #1922. I can rebase once you’ve merged his code if you want.

#7
Updated by James Turnbull about 3 years ago

  • Status changed from Ready For Checkin to Closed

Pushed in commit:32c2be926795ce3ce68f573367f7700e87ac8416 in branch 0.24.x

Also available in: Atom PDF