The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com
Need test to guarantee that facts are written to fact YAML and inventory service database BEFORE node is classified
|Affected Puppet version:||Branch:|
Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com
This ticket may be automatically exported to the PUP project on JIRA using the button below:
My understanding is that we currently always write the node fact YAML and the inventory service database entry before the ENC gets called, but it’s considered a fortuitous coincidence and we don’t make any guarantees about the order.
Since some people use facts in their ENCs, and it’s an elegant solution to things that are impossible to do by hostname a lot of the time, we should guarantee that facts get written in both places before the ENC gets called. This should be backed with a spec test.
- When we can’t write to YAML on disk, Nigel thinks we blow up weirdly, which is reasonable in cases where our disk is full, right?
- What happens when we can’t write to the inventory service? Fail with a big warning in the logs?