system-config/playbooks/roles/zuul-executor
Clark Boylan 183e186fe0 Fix error checking with zuul graceful stops
The previous code had attempted to handle the case where the container
isn't running and we exec a zuul graceful stop in the container.
Unfortunately I got the string to check for wrong. I think I must've
checked the `docker exec` output and not the `docker-compose exec`
output.

This change updates the string to match exactly what ansible complained
about:

  TASK [zuul-merger : Gracefully stop Zuul Merger] *******************************
  fatal: [zm05.opendev.org]: FAILED! => {
      "changed": true,
      "cmd": "docker-compose exec merger zuul-merger stop",
      "delta": "0:00:00.573561",
      "end": "2022-09-14 01:59:41.721044",
      "failed_when_result": true,
      "rc": 1,
      "start": "2022-09-14 01:59:41.147483"
  }

  STDERR:

  No container found for merger_1

  MSG:

  non-zero return code

Specifically we check for 'No container found' in stderr.

Change-Id: I737b9da14c210215926804816d1e032540d694dc
2022-09-14 08:12:59 -07:00
..
defaults Run zuul-executor using docker 2020-06-09 14:26:38 -05:00
files zuul-*: use multiline formatter 2021-12-13 14:54:16 +11:00
tasks Fix error checking with zuul graceful stops 2022-09-14 08:12:59 -07:00
templates Remove orphaned zuul-executor defaults file 2021-01-30 11:17:54 -08:00
vars Run zuul-executor using docker 2020-06-09 14:26:38 -05:00
README.rst Run Zuul using Ansible and Containers 2020-04-24 09:18:44 -05:00

Run Zuul Executor