puppet facts and mcollective are incompatible

[Fabrice Bacchella]

I used to fill mcollective yaml facts with a simple facter -p > foo.yaml.

But with facter 3, -p is gone, one should use 'puppet facts --render-as yaml' instead.

So far so good, but mcollective can't use this command output :
yaml_facts.rb:31:in `rescue in block in load_facts_from_source' Failed to load yaml facts from /var/cache/mcollective/facts.yaml: TypeError: no implicit conversion of Puppet::Node::Facts into Hash

Indeed, the output is:
--- !ruby/object:Puppet::Node::Facts
name: <FQDN>
values:
...
fact values
...

How can I filter the output and get only the values ?

[Fabrice Bacchella]

And I can use puppet to generate it, I don't run puppet with cron or as a daemon.

> --
> You received this message because you are subscribed to the Google Groups "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/DA7BE0C4-8AFF-4D9C-9834-C65BD2E64F9B%40orange.fr.
> For more options, visit https://groups.google.com/d/optout.

[Peter Huene]

On Monday, July 20, 2015 at 2:12:45 PM UTC-7, Fabrice Bacchella wrote:

I used to fill mcollective yaml facts with a simple facter -p > foo.yaml.

But with facter 3, -p is gone, one should use 'puppet facts --render-as yaml' instead.

For this (and a few other reasons), the breaking change of removing the -p switch in Facter 3.0.0 is being reverted in 3.0.2, which will be released very soon.

Unfortunately I don't know of a good workaround that is possible with the "puppet facts" command given your intended usage.

[Fabrice Bacchella]

>
> For this (and a few other reasons), the breaking change of removing the -p switch in Facter 3.0.0 is being reverted in 3.0.2, which will be released very soon.
>

When do you expect it to be released ?

I've found many bugs with facter 3 (and I've been using it only for a few days), where can I found the list of closed bugs for this release ?

[Peter Huene]

On Tue, Jul 21, 2015 at 1:27 AM, Fabrice Bacchella <fabrice....@orange.fr> wrote:

>
> For this (and a few other reasons), the breaking change of removing the -p switch in Facter 3.0.0 is being reverted in 3.0.2, which will be released very soon.
>

When do you expect it to be released ?

Within a few days, hopefully.

 

I've found many bugs with facter 3 (and I've been using it only for a few days), where can I found the list of closed bugs for this release ?

Here's a list of what's been addressed in 3.0.2:  https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20FACT%20AND%20fixVersion%20%3D%20%22FACT%203.0.2%22

There have been a number of regression fixes including fixes to command execution, inclusion of the -p option, porting the xendomains fact, OS fact fixes, and the fqdn fact reporting incorrectly on some systems.

If there's an issue you're running into that you don't see being addressed in this release, please file a ticket describing your problem and let me know the ticket number and I'll see what I can do to address the problem.  Thanks!

 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/57D60F90-53A6-403A-922B-39A07A58AE12%40orange.fr.

For more options, visit https://groups.google.com/d/optout.

--

Join us at PuppetConf 2015, October 5-9 in Portland, OR - www.2015.puppetconf.com 

Register early to save 40%!

[Fabrice Bacchella]

> There have been a number of regression fixes including fixes to command execution, inclusion of the -p option, porting the xendomains fact, OS fact fixes, and the fqdn fact reporting incorrectly on some systems.
>
> If there's an issue you're running into that you don't see being addressed in this release, please file a ticket describing your problem and let me know the ticket number and I'll see what I can do to address the problem. Thanks!

Here one:
https://tickets.puppetlabs.com/browse/FACT-1137