From 01f30d523b8b54336b59f097c00b521dc67eee95 Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Tue, 2 Feb 2016 08:16:57 -0800 Subject: [PATCH] Temporarily stop releasing after bandersnatch We're in the middle of a long initial vos release to a new RO site and we don't want the bandersnatch cron to accidentally start a new one when this finishes. Instead, we want to manually release until we are certain that the release runtime is down to a manageable level. Change-Id: Ib5af8d3bbd4439fc414e6df87e6f8b37807fa138 --- .../openstack_project/files/bandersnatch-mirror-update.sh | 7 ------- 1 file changed, 7 deletions(-) diff --git a/modules/openstack_project/files/bandersnatch-mirror-update.sh b/modules/openstack_project/files/bandersnatch-mirror-update.sh index 7fa0a00c73..6bb32c2629 100644 --- a/modules/openstack_project/files/bandersnatch-mirror-update.sh +++ b/modules/openstack_project/files/bandersnatch-mirror-update.sh @@ -17,11 +17,4 @@ echo "Obtaining bandersnatch tokens and running bandersnatch." k5start -t -f /etc/bandersnatch.keytab service/bandersnatch -- timeout -k 2m 30m run-bandersnatch -RET=$? - -if [ $RET -eq 0 ]; then - echo "Bandersnatch completed successfully, running vos release." - k5start -t -f /etc/afsadmin.keytab service/afsadmin -- vos release mirror.pypi -fi - echo "Done."