From cc74e674db58af26ceea63a8bbb3007835ad497d Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Wed, 27 Oct 2021 15:00:03 -0700 Subject: [PATCH] Limit zuul stop/start playbooks to zuul02 Rather than restarting the whole scheduler group, just restart zuul02, which is our only production scheduler. That will allow us to boot zuul01 as a secondary scheduler and manually add/remove it for testing. Once we can reliably run two schedulers, we can revert this change. Change-Id: I5518ea1d3a6a1d48460b0436d4d1eaf9d52b7ddb --- playbooks/zuul_start.yaml | 2 +- playbooks/zuul_stop.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/playbooks/zuul_start.yaml b/playbooks/zuul_start.yaml index 8865a6d996..4426ce6185 100644 --- a/playbooks/zuul_start.yaml +++ b/playbooks/zuul_start.yaml @@ -1,6 +1,6 @@ # Run this with "-f 20" -- hosts: 'zuul-scheduler:!disabled' +- hosts: 'zuul02.opendev.org:!disabled' tasks: - include_role: name: zuul-scheduler diff --git a/playbooks/zuul_stop.yaml b/playbooks/zuul_stop.yaml index 58aeaa42bb..d8c12c8de3 100644 --- a/playbooks/zuul_stop.yaml +++ b/playbooks/zuul_stop.yaml @@ -1,6 +1,6 @@ # Run this with "-f 20" -- hosts: 'zuul-scheduler:!disabled' +- hosts: 'zuul02.opendev.org:!disabled' any_errors_fatal: true tasks: - include_role: