Issue #4207 has been reported by Brice Figureau. ---------------------------------------- Bug #4207: Storeconfigs save the whole yaml catalog in the hosts entry http://projects.puppetlabs.com/issues/4207
Author: Brice Figureau Status: Unreviewed Priority: High Assigned to: Category: stored configuration Target version: 2.6.0 Affected version: 2.6.0rc1 Keywords: Branch: During storeconfigs serialization, one part updates/stores the hosts table for the current node entry. It particularly stores the node environment as a string. Unfortunately it seems we now pass an environment instance and not the environment name which, so the active record layer yamlize the environment instance before storing it. Unfortunately again, the environment has apparently a reference to the catalog, so we store the full catalog :-) Here's the start of the update sql request issued for MySQL: <pre> UPDATE `hosts` SET `updated_at` = '2010-07-10 16:17:10', `last_compile` = '2010-07-10 16:17:10', `environment` = '--- &id046 !ruby/object:Puppet::Node::Environment\n cache_timestamp: 2010-07-10 16:13:20.916429 +02:00\n known_resource_types: &id001 !ruby/object:Puppet::Resource::TypeCollection\n definitions: \n glusterfs::client::volume: !ruby/object:Puppet::Resource::Type\n arguments: \n server: \n mntpoint: \n code: !ruby/object:Puppet::Parser::AST::ASTArray\n children: \n... </pre> -- 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.
