oVirt infra daily report - unstable production jobs - 711

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/711//artifact/exported-artifacts/upstream_report.html Cheers, Jenkins

[JIRA] (OVIRT-2556) kubevirt test runs and nested docker issue

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri closed OVIRT-2556. Resolution: Cannot Reproduce (was: Fixed) No replies on the ticket, please reopen if still relevant > ku

Jenkins build is back to normal : system-sync_mirrors-fedora-updates-fc27-x86_64 #1280

See ___ Infra mailing list -- infra@ovirt.org To unsubscribe send an email to infra-le...@ovirt.org Privacy Statement: https://www.ovirt.org/

[JIRA] (OVIRT-2631) [VDSM] Build fail with "Curl error (28): Timeout was reached for..."

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2631: - Resolution: Cannot Reproduce Status: Done (was: To Do) looks like a network outage that caused

[JIRA] (OVIRT-2644) [VDSM] Error in CI check-patch linter

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2644: - Resolution: Won't Fix Status: Done (was: To Do) seems to be related to broken copr repos, not i

[JIRA] (OVIRT-2645) [VDSM] Tests mounting loop devices fail randomly again

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2645: - Resolution: Fixed Status: Done (was: To Do) please reopen if issue wasn't solved > [VDSM] Test

[JIRA] (OVIRT-2648) Failing Jenkins job

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2648: - Resolution: Fixed Status: Done (was: To Do) > Failing Jenkins job > --- > >

[JIRA] (OVIRT-2651) All vdsm builds fail now

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2651: - Resolution: Fixed Status: Done (was: To Do) seem like problem was solved (due to pinning to sam

[JIRA] (OVIRT-2654) Kubvirt jobs stuck for one day

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eyal Edri updated OVIRT-2654: - Resolution: Done Status: Done (was: To Do) not related to the load. > Kubvirt jobs stuck for o

Re: Status of 4.3 CQ and OST 4.3

On Sun, Jan 20, 2019 at 1:53 PM Sandro Bonazzola wrote: > > > Il giorno dom 20 gen 2019, 10:20 Eyal Edri ha scritto: > >> I see we've added 4.3 CQ to Jenkins, but we didn't add 4.3 OST suites >> yet, so I assume we're using the master ones? >> >> Should we add 4.3 suites? or keep using the maste

Re: Status of 4.3 CQ and OST 4.3

Il giorno dom 20 gen 2019, 10:20 Eyal Edri ha scritto: > I see we've added 4.3 CQ to Jenkins, but we didn't add 4.3 OST suites yet, > so I assume we're using the master ones? > > Should we add 4.3 suites? or keep using the master suite since we don't > expect too many changes to happen in the nea

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=38854#comment-38854 ] Daniel Belenky commented on OVIRT-2656: --- I'm checking On Sun, Jan 20, 2019 at 10:30 AM

[JIRA] (OVIRT-2656) Upstream-sources trigger for ovirt-engine-metrics does not work

Shirly Radco created OVIRT-2656: --- Summary: Upstream-sources trigger for ovirt-engine-metrics does not work Key: OVIRT-2656 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2656 Project: oVirt - virtua

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc27-x86_64 #1279

See Changes: [Evgheni Dereveanchin] move jenkins check_patch from fc27 to fc29 [Ehud Yonasi] mirror_sync: add gluster5 to mirrors. -- Started

Status of 4.3 CQ and OST 4.3

I see we've added 4.3 CQ to Jenkins, but we didn't add 4.3 OST suites yet, so I assume we're using the master ones? Should we add 4.3 suites? or keep using the master suite since we don't expect too many changes to happen in the near future? -- Eyal edri MANAGER RHV/CNV DevOps EMEA VIRTUALI