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@redhat.com> wrote:Hi Nir,There has been an issue today caused by our configuration management system (puppet) that accidentally downgraded Jenkins which caused some plugin configs to be wiped.This caused the issue you see as new workers can't start and process the queue. I've recovered the old config from bacup and am now working on restoring Jenkins operation.Will update you once the problem is resolved. The tracker ticket is here:Sorry for the inconvenience caused.On Wed, Aug 14, 2019 at 6:58 PM Nir Soffer <nsoffer@redhat.com> wrote:_______________________________________________After waiting for build-artifacts job for 36 minutes (typically finish in 15 minutes)I found that jeknins seems to be broken.We depend on CI and OST for merging patches.Can someone check this?---
Devel mailing list -- devel@ovirt.org
To unsubscribe send an email to devel-leave@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/7TXF7RYGFYGWB4JXQDCKQMMN2EEW3X2I/
--Regards,Evgheni Dereveanchin--Regards,Evgheni Dereveanchin