It now tries to serialise the result of each host for some reason:
krenair@deployment-cumin:~$ sudo cumin --force --output json 'P{deployment-cumin.deployment-prep.eqiad.wmflabs}' id
1 hosts will be targeted:
deployment-cumin.deployment-prep.eqiad.wmflabs
FORCE mode enabled, continuing without confirmation
----- OUTPUT of 'id' -----
uid=0(root) gid=0(root) groups=0(root)
================
PASS: |███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 100% (1/1) [00:01<00:00, 1.73s/hosts]
FAIL: | | 0% (0/1) [00:01<?, ?hosts/s]
100.0% (1/1) success ratio (>= 100.0% threshold) for command: 'id'.
100.0% (1/1) success ratio (>= 100.0% threshold) of nodes successfully executed all commands.
_____FORMATTED_OUTPUT_____
Caught TypeError exception: b'uid=0(root) gid=0(root) groups=0(root)' is not JSON serializableThis has broken my cron job that emails me about the puppet results across all our deployment-prep hosts, as it tries to shell out to cumin and gather the results after _____FORMATTED_OUTPUT_____\n as JSON.