Jenkins is back in operation after restoring configs and restarting it.
New jobs should be processed normally. Older ones that partially ran when
the restart happened may fail - please re-trigger those.
There is still an issue with the s390x VM that we use for CI. It is
unrelated to the Jenkins outage: looks like the mainframe it's hosted on is
overloaded.
Until the load drops it won't be able to run CI jobs so some jobs that
build for this platform (mostly VDSM) may be stuck in the queue.
The VM belongs to the Fedora project and we share access to it with several
other projects.
I'll try to reach out to Fedora about this issue but if it persists we may
need to temporarily disable s390x jobs.
On Wed, Aug 14, 2019 at 7:11 PM Evgheni Dereveanchin <ederevea(a)redhat.com>
wrote: