:: sigh ::: Back to the ol' drawing board. LOL.
Well I guess that's what I get by assuming that it will remain text, and not use macros. Silly me. Thank you so much for your help! On Wed, Feb 15, 2012 at 11:58 AM, Daniel Pittman <[email protected]>wrote: > Hey. So, to answer your questions in reverse order: > > There is almost certainly no way to get the "old behaviour" back > without running the older software. This isn't something we are > deliberately doing, it is a property of the YAML encoder, which is > working absolutely as designed. > > You should read the content by ... using an YAML reader. There are > YAML libraries for pretty much any language you want to use, and that > will get the data out. > > If you *are* using a YAML reader, and you don't get that back, you are > welcome to report a bug - attach the problem file, and include full > details of what YAML reader you are using, and we can check if there > is some unexpected corruption going on or something. > > If you are not, and were reading it as some sort of textual content > without doing the full YAML decoding pass, then stop. Use a YAML > reader. :) > > On Wed, Feb 15, 2012 at 07:44, Marek Dohojda <[email protected]> wrote: > > PS... is there any way to revert it back to the old behavior? (I am not > > seeing this on RHEL5 with older Ruby). > > > > -----Original Message----- From: Marek Dohojda > > Sent: Tuesday, February 14, 2012 10:11 PM > > > > To: [email protected] > > Subject: Re: [Puppet Users] Yaml server facts, weird message: "id00" > > > > The problem I am having is that I am using this to pull inventory from > the > > puppet server. I don't want to use mcollective since when server is > down I > > can't get inventory. I been using this for a long time, without an > issue. > > Not sure if this is RHEL6 issue or what? > > > > So how can I read the actual data from the yaml? > > > > (Sorry if I sound like a newbe) > > > > On the server I am read this information: > > puppet: 2.7.6-2 > > ruby: 1.8.5-22 > > RHEL: 5 > > > > "client" server: > > puppet: 2.7.10-1 > > ruby: 1.8.7.352-4 > > RHEL: 6 > > > > Thank you! > > > > > > -----Original Message----- From: Daniel Pittman > > Sent: Tuesday, February 14, 2012 5:06 PM > > To: [email protected] > > Subject: Re: [Puppet Users] Yaml server facts, weird message: "id00" > > > > 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. > > -- > > 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. > > > > > > -- > 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. > > -- 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.
