From ddd65268d5646c45f204dcebd749f69ba149ef74 Mon Sep 17 00:00:00 2001
From: Pavel Raiskup <praiskup@redhat.com>
Date: Fri, 11 Feb 2022 10:45:35 +0100
Subject: [PATCH] copr-builders: s390x machines can be started in jp-tok-2, too

IBM support team cleaned-up some leftover volumes, so we can start the
machines in this location again!
---
 roles/copr/backend/templates/resalloc/pools.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/roles/copr/backend/templates/resalloc/pools.yaml b/roles/copr/backend/templates/resalloc/pools.yaml
index 4ec0c1e814..6e512ebd53 100644
--- a/roles/copr/backend/templates/resalloc/pools.yaml
+++ b/roles/copr/backend/templates/resalloc/pools.yaml
@@ -141,7 +141,7 @@ copr_ibm_cloud_s390x_tokyo_{% if devel %}dev{% else %}prod{% endif %}:
     - arch_s390x_native
     - ibm_cloud
     - tokyo
-  cmd_new: '/var/lib/resallocserver/resalloc_provision/ibm-cloud-vm --log-level debug create "$RESALLOC_NAME" --zones jp-tok-1,jp-tok-3'
+  cmd_new: '/var/lib/resallocserver/resalloc_provision/ibm-cloud-vm --log-level debug create "$RESALLOC_NAME"'
   cmd_delete: "/var/lib/resallocserver/resalloc_provision/vm-delete"
   cmd_livecheck: "resalloc-check-vm-ip"
   cmd_release: "/var/lib/resallocserver/resalloc_provision/vm-release"