Issue #8373 has been updated by Brice Figureau. Status changed from Needs Decision to Investigating
That's strange. I read the code and definitely we accumulate tag names in the puppet_tags table. I'll check later what is wrong. The differences between thin_storeconfigs and storeconfigs are pretty minimal (it just saves the exported resources instead of all resources), and I fail to see why it wouldn't save the tags along with the resources. It might be a difference or change in rails itself. What rails version are you running? That'd be great if you could activate the puppet railslog and attach the various sql requests issued in thin_storeconfigs mode (on a pristine database, so that we can see what is not done). ---------------------------------------- Bug #8373: Using thin_storeconfigs causes custom tags not to be treated as tags. https://projects.puppetlabs.com/issues/8373 Author: Rutger Spiertz Status: Investigating Priority: Normal Assignee: Brice Figureau Category: stored configuration Target version: Affected Puppet version: Keywords: Branch: Setup: Puppetmaster 2.6.8 with Passenger Activemq 5.4.1 Without thin_storeconfigs custom tags are added to the puppet_tags table in the db, thus allowing importing of exported resources using those tags as filter. When thin_storeconfigs is set to true the custom tag only shows up in the param_values table, but is never added to puppet_tags, which prevents importing those resources when filtering on the custom tag. Example: On host a: file { "foo": tag => "bar"; } On host b: File <<| tag == "bar" |>> This will work without thin_storeconfigs set to false, but not when it's set to true. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
