From f9ab2b82dfc2161069135b1137540c643b44a454 Mon Sep 17 00:00:00 2001 From: Miroslav Suchý Date: Jan 13 2015 11:47:51 +0000 Subject: enhance troubleshooting part of copr --- diff --git a/copr.txt b/copr.txt index f0a2729..3904dd6 100644 --- a/copr.txt +++ b/copr.txt @@ -9,7 +9,7 @@ Copr Package singer: http://copr-keygen.cloud.fedoraproject.org/ - Devel instances: + Devel instances (NO NEED TO CARE ABOUT THEM, JUST THOSE ABOVE): http://copr-fe-dev.cloud.fedoraproject.org/ http://copr-be-dev.cloud.fedoraproject.org/ http://copr-keygen-dev.cloud.fedoraproject.org/ @@ -24,6 +24,40 @@ Contact Information Purpose: Build system +TROUBLESHOOTING: + + Almost every problem with Copr is due problem in OpenStack, in such case: + ssh root@copr-be.cloud.fedoraproject.org + systemctl stop copr-backend + source /home/copr/cloud/ec2rc.sh + /home/copr/delete-forgotten-instances.pl + wait a minute and check + euca-describe-instances + sometimes you have to run delete-forgotten-instances.pl as openstack is + sometimes stuborn. + systemctl start copr-backend + + If this does not help you, then stop and kill all OpenStack VM builders + and: + ssh root@fed-cloud02.cloud.fedoraproject.org + source keystonerc + for i in $(nova-manage floating list | grep 7ed4d | grep None | sort | awk +'{ print $2}'); do nova-manage floating delete $i; nova-manage floating create +$i; done + or even (USUALLY NOT NEEDED): + for i in /etc/init.d/openstack-*; do $i condrestart; done + and then start copr backend service again. + + Sometimes OpenStack can not handle spawning too much VM at the same time. + So it is safer to edit on copr-be.cloud.fedoraproject.org: + vi /etc/copr/copr-be.conf + and change: + group0_max_workers=12 + to "6". Start copr-backend service and some time later increase it to + original value. Copr automaticaly detect change in script and increase + number of workers. + + Deploy informations: Using playbooks and rbac: