The [depool / pool conftool scripts](https://github.com/wikimedia/operations-puppet/tree/7de806344f358b0364001dd05d7d7c6dbe03e235/modules/conftool/templates) are used during Scap3 service deploys to depool and repool the target hosts before and after a service restart, respectively. However, in certain occasions the hosts are not actually (r|d)epooled, in spite of the scripts exiting with the `0` exit code. This effect has been observed during Parsoid deploys. Specifically, some hosts were not repooled by Pybal, and when a second `depool` command was issued, the script reported that its state has been changed from `pooled=no` to `pooled=yes`. The specifics of why this is occurring need to be investigated and fixed.
In the short term, we need to find a way to reliably check if a host has been (r|d)epooled and act accordingly (wait, force the command one more time, etc).