741f5b333d
There are two issues in the zuul merger and executor shutdowns. The first is that `docker-compose ps -q` will report exited containers unlike `docker ps -q`. This means we may try to exec into a non running container which is an error. Handle this by checking the error message and proceeding if the 'is not running' string is present. The second issue is a race between stopping a container and running an exec in the container. If a container stops while an exec is running in it that exec appears to be treated with some equivalent of kill -9. The result is the exec returns 137. While theoretically possible for both executor and merger graceful stop command we seem to only hit this with the merger so we handle exit code 137 for the merger only. This way we'll get info if the executors start running into this too. Change-Id: Ia6dc2d7e397631d72968ffa89c4492b803c89c47 |
||
|---|---|---|
| .. | ||
| defaults | ||
| files | ||
| tasks | ||
| templates | ||
| vars | ||
| README.rst | ||
Run Zuul Executor