Closed sabaini closed 2 years ago
Thanks for reporting @sabaini! To help me repro (and to add to the itests), could you dump the juju debug-log --replay to a file and attach it here?
Sure -- here you go: juju-log-replay.txt.gz
Humm, there are several odd things about that log trace. Firstly, I can only see 'update-status', secondly the log formatting is not one I'm familiar with. I see the uniter event log line goes: "(via explicit, bespoke hook script)", which I've never seen before. That is not a format that jhack tail supports ATM, so even if it didn't crash there, I doubt it would pick any logs up.
Did you set model-config logging-config="<root>=WARNING;unit=DEBUG"
? (you should)
I managed to reproduce the issue deploying ceilometer + prometheus-node-exporter as a subordinate, there is indeed an issue there. Troubleshooting...
Fixed it! It was indeed an issue with parsing the status when it included subordinate charms.
@sabaini could you verify that #17 solves the issue?
Indeed it does, thank you!
Afaict
jhack tail
parsing ofjuju status
chokes on subordinates.When running
jhack tail
against a model full of machine charms (OpenStack) I'm getting this traceback