-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fail to return facts with Puppet 5.5 #163
Comments
With Puppet 5.5, the refresh_facts.rb produce a YAML file containing aliases, which are not properly processed (choria-legacy/mcollective-choria#455). This workaround prevents the same object to be assigned to mcollective::client::libdir and mcollective::server::libdir by duplicating them. The Psych serializer then consider them as two distinct objects and does not emit an alias.
Confirmed, I suffer from this issue, and this patch works for me (Ubuntu 16.04, Puppet 5.5, etc). Making the suggested change on the host and restarting the 'mcollective' service makes all my facts magically come back. Thanks so much! |
(#163) Workaround for YAML aliasing
Cool that it is fixed here as well. However keep in mind guys, that any other modules or custom facts may break too. This bug is fixed upstream already (puppetlabs/marionette-collective#474), but if someone needs more flexible workaround, here it is:
|
soonish I'll update the fact export script to write a JSON file as well and switch to JSON :) |
As reported in choria-legacy/mcollective-choria#455 , after updating to Puppet 5.5, facts reporting got broken:
The logging system reports a problem related to aliasing:
In my
generated-facts.yaml
file,mcollective::server::libdir
is aliased to the value ofmcollective::client::libdir
.The text was updated successfully, but these errors were encountered: