On Tue, Feb 14, 2012 at 15:52, chrobry <[email protected]> wrote: > I looked on google, and here but can't seem to find a solution to my > issue.
You don't have an issue. ;) > I just deployed puppet to few servers, rhel6.1, and my /var/lib/puppet/ > yaml/facts are having some weird variables in them. > For instance on one of my servers server.yaml here is what I see: > > puppetversion: *id001 > selinux_mode: &id003 targeted > memorysize: *id002 > > Could someone please point me towards the direction of what I am doing > wrong? You mistakenly thought that YAML was intended for human consumption, which is absolutely not the case. That is a secondary priority, following on from "fully serialize a graph of objects". So, those are references to already defined values, and are emitted to allow shared object references and/or compress memory consumption. Your data contains multiple references to the same object, and YAML reflected that. Nothing to worry about here. Those should expand when loaded correctly. > PS. I deleted the files, and recreated them with same results. In > addition on mcollective facts.yaml the same (bad) information appears. That, though, could be a problem. Are you saying that when you use mcollective it sees `&id001` as the value of that fact? Can you show how you are invoking mcollective, and a demonstration of the output around the problem? Also, which versions of Ruby, and MCollective, are you using? -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" 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-users?hl=en.
