Travis Glenn Hansen

This is an example response from CI: ``` { "id": "tank/ci/ce25fabf/v", "type": "FILESYSTEM", "name": "tank/ci/ce25fabf/v", "pool": "tank", "encrypted": false, "encryption_***": null, "key_loaded": false, "children": [], ... ``` If you search...

I can't get that link to open :(

hmm, I don't see that error in the output. Can you recreate the error and send over the respective logs?

We need to turn on debug logging so you see the raw requests/responses :( this issue seems really odd. I can add a small snippet of code to maybe try...

Well that response seems to have completed successfully. Can you run those logs out further to the point where the cleaner breaks?

Make sure to run the cleaner from the controller pod if that's not clear.

No. I looked through the previous logs sent and still cannot find a response where the children attribute is not present. Crazy stuff. If you actually did the clean operation...

There are no downsides if you don't mind allowing ssh access to the node. I would like to discover the issue. The last set of logs you sent do not...

Can you also send over your full config (cleansed of secrets of course)?

Can you enable `ipc=host` on the container and see if that clears it up?