| PuppetDB's export can terminate early without error message. It will write a valid tar file of what it have exported, but the file misses all facts and maybe some of catalogs and/or reports. I've verified that this happens with both the puppetdb-cli tool and with curl when using the anonymization profile full. And I caused this behavior on 1262e5f1165c00cb22b51ab5fab5649bda759a64 the current HEAD of master as well as dec3ac399c4c776f623efdc16e96605cfec32ae4, which is before we added support for exporting catalog-inputs to verify we did not introduce the bug. When using no anonymization (level is none) this bug does not happen. I have not tested the intermediate levels low and moderate. The dataset that caused the error was 100 nodes with 10 reports each generated by benchmark. When testing using 1 node with 1 report, all the data was properly exported at both none and full anonymization. This leads me to believe that somewhere in the anonymization code an error is thrown that gets caught and ignored before it is logged. In the logs you'll see a log message like
2019-10-07 12:07:20,643 INFO [clojure-agent-send-off-pool-0] [p.p.export] Export triggered for PuppetDB
|
But if the process terminates early, you will not see the ending log message.
2019-10-07 12:07:20,978 INFO [clojure-agent-send-off-pool-0] [p.p.export] Finished exporting PuppetDB
|
|
