[10:29] <LocutusOfBorg> hello, looks like bos01(s390x) is stuck in some sort of cleaning loop
[10:30] <LocutusOfBorg> (maybe also others)
[10:35] <cjwatson> That's why we have two regions :)
[10:38] <cjwatson> bos01-s390x has been fairly sad for some time - I haven't been putting too much effort into it since IIRC there's a plan to shift hardware over to PS6
[10:38] <LocutusOfBorg> well, bos02 was "disabled" :) 
[10:38] <cjwatson> Yeah, I just poked that.
[10:38] <LocutusOfBorg> now looks like situation will shortly improve, thanks
[10:39] <LocutusOfBorg> and yay for hw upgrade!
[10:39] <cjwatson> (This is partly because the usual auto-reset job is currently disabled while IS does some debugging on bos03.()
[10:40] <LocutusOfBorg> thanks
[10:41] <cjwatson> I'm not sure whether it's going to be a hardware upgrade or just redeployment
[11:24] <LocutusOfBorg> sadly looks bos02 is broken again
[11:30] <cjwatson> I'll poke it occasionally, but I'm not going to play manual cron, sorry.  Once IS has finished with their debugging I'll turn the automatic job on again.
[12:01] <cjwatson> IS did some repair work on bos02-s390x, so should be a bit healthier.