- Infra - oVirt List Archives

[CQ]: 108917, 2 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 May '20

12 May '20

A system test invoked by the "ovirt-master" change queue including change 108917,2 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 108916,3 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108916,3 (ovirt-imageio) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108917/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108916/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23646/

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.3 - Build #1 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 May '20

12 May '20

Build: https://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.3/1/, Build Number: 1, Build Status: FAILURE

1 4

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #7 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 12 May '20

12 May '20

Build: https://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/7/, Build Number: 7, Build Status: FAILURE

1 4

[CQ]: 108923, 1 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 May '20

12 May '20

A system test invoked by the "ovirt-master" change queue including change 108923,1 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 108916,3 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108916,3 (ovirt-imageio) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108923/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108916/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23643/

1 0

oVirt infra daily report - unstable production jobs - 1188
by jenkins＠jenkins.phx.ovirt.org 12 May '20

12 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1188//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 108915, 3 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 12 May '20

12 May '20

A system test invoked by the "ovirt-master" change queue including change 108915,3 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 108916,3 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108916,3 (ovirt-imageio) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108915/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108916/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23640/

1 0

Ovirt host GetGlusterVolumeHealInfoVDS failed events
by srivathsa.puliyala＠dunami.com 11 May '20

11 May '20

Hi, We have a oVirt cluster with 4 hosts and hosted engine running on one of them (all the nodes provide the storage with GlusterFS) Currently there are 53 VMs running. The version of the oVirt-Engine is 4.2.8.2-1.el7 and GlusterFS is 3.12.15. From past 1 week, we seem to have multiple events popping up on Ovirt-UI about the GetGlusterVolumeHealInfoVDS from all the nodes randomly like one ERROR event for every ~13minutes. Sample Event dashboard example: May 4, 2020, 2:32:14 PM - Status of host <host-1> was set to Up. May 4, 2020, 2:32:11 PM - Manually synced the storage devices from host <host-1> May 4, 2020, 2:31:55 PM - Host <host-1> is not responding. Host cannot be fenced automatically because power management for the host is disabled. May 4, 2020, 2:31:55 PM - VDSM <host-1> command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues May 4, 2020, 2:19:14 PM - Status of host <host-2> was set to Up. May 4, 2020, 2:19:12 PM - Manually synced the storage devices from host <host-2> May 4, 2020, 2:18:49 PM - Host <host-2> is not responding. Host cannot be fenced automatically because power management for the host is disabled. May 4, 2020, 2:18:49 PM - VDSM <host-2> command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues May 4, 2020, 2:05:55 PM - Status of host <host-2> was set to Up. May 4, 2020, 2:05:54 PM - Manually synced the storage devices from host <host-2> May 4, 2020, 2:05:35 PM - Host <host-2> is not responding. Host cannot be fenced automatically because power management for the host is disabled. May 4, 2020, 2:05:35 PM - VDSM <host-2> command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues May 4, 2020, 1:52:45 PM - Status of host <host-3> was set to Up. May 4, 2020, 1:52:44 PM - Manually synced the storage devices from host <host-3> May 4, 2020, 1:52:22 PM - Host <host-3> is not responding. Host cannot be fenced automatically because power management for the host is disabled. May 4, 2020, 1:52:22 PM - VDSM <host-3> command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues May 4, 2020, 1:39:11 PM - Status of host <host-4> was set to Up. May 4, 2020, 1:39:11 PM - Manually synced the storage devices from host <host-4> May 4, 2020, 1:39:11 PM - Host <host-4> is not responding. Host cannot be fenced automatically because power management for the host is disabled. May 4, 2020, 1:39:11 PM - VDSM <host-4> command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues May 4, 2020, 1:26:29 PM - Status of host <host-3> was set to Up. May 4, 2020, 1:26:28 PM - Manually synced the storage devices from host <host-3> May 4, 2020, 1:26:11 PM - Host <host-3> is not responding. Host cannot be fenced automatically because power management for the host is disabled. May 4, 2020, 1:26:11 PM - VDSM <host-3> command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues May 4, 2020, 1:13:10 PM - Status of host <host-1> was set to Up. May 4, 2020, 1:13:08 PM - Manually synced the storage devices from host <host-1> May 4, 2020, 1:12:51 PM - Host <host-1> is not responding. Host cannot be fenced automatically because power management for the host is disabled. May 4, 2020, 1:12:51 PM - VDSM <host-1> command GetGlusterVolumeHealInfoVDS failed: Message timeout which can be caused by communication issues and so on..... When I look at the Compute > Hosts dashboard, I see the host status to be DOWN when VDSM event (GetGlusterVolumeHealInfoVDS failed) is popped and automatically the host status is set to UP within no time. FYI: when host status is DOWN, the VM's running on that host are not migrating and everything is running perfectly fine. This is happening all day. Is there something I can troubleshoot? Appreciate your comments.

1 1

[CQ]: 108916,3 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 11 May '20

11 May '20

Change 108916,3 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/108916/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23637/

1 0

Re: [ovirt-devel] oVirt and Fedora
by Michal Skrivanek 11 May '20

11 May '20

> On 11 May 2020, at 14:49, Neal Gompa <ngompa13(a)gmail.com> wrote: > > On Mon, May 11, 2020 at 8:32 AM Nir Soffer <nsoffer(a)redhat.com> wrote: >> >> On Mon, May 11, 2020 at 2:24 PM Neal Gompa <ngompa13(a)gmail.com> wrote: >>> >>> As far as the oVirt software keeping up with Fedora, the main problem here has always been that people aren't integrating their software into the distribution itself. it was never a good fit for oVirt to be part of other distributions. We had individual packages part of Fedora in history, but there are things which are hard to accept (like automatically enabling of installed services, UIDs), and overall it’s just too complex, we’re rather a distribution than a simple app on top of base OS. >>> That's how everything can get tested together. And this comes back to the old bug about fixing vdsm so that it doesn't use /rhev, but instead something FHS-compliant (RHBZ#1369102). Once that is resolved, pretty much the entire stack can go into Fedora. And then you benefit from the Fedora community being able to use, test, and contribute to the oVirt project. As it stands, why would anyone do this for you when you don't even run on the cutting edge platform that feeds into Red Hat Enterprise Linux? >> >> This was actually fixed a long time ago. With this commit: >> https://github.com/oVirt/vdsm/commit/67ba9c4bc860840d6e103fe604b16f494f60a0… >> >> You can configure a compatible vdsm that does not use /rhev. >> >> Of course it is not backward compatible, for this we need much more >> work to support live migration >> between old and new vdsm using different data-center configurations. >> > > It'd probably be simpler to just *change* it to an FHS-compatible path > going forward with EL8 and Fedora and set up a migration path there, > but it's a bit late for that... :( It wouldn’t. We always support live migration across several versions (now it’s 4.2-4.4) and it needs to stay the same or youo have to go with arcane code to mangle it back and forth which gets a bit ugly when you consider suspend/resume, snapshots, etc > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/SBAZ2F3FCOVGH…

1 0

[CQ]: 108934,2 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 11 May '20

11 May '20

Change 108934,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/108934/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23634/

1 0

Re: [ovirt-devel] Re: oVirt and Fedora
by Nir Soffer 11 May '20

11 May '20

On Mon, May 11, 2020 at 2:24 PM Neal Gompa <ngompa13(a)gmail.com> wrote: > > On Mon, May 11, 2020 at 2:16 AM Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >> >> If you have followed the oVirt project for a few releases you already know oVirt has struggled to keep the pace with the fast innovation cycles Fedora Project is following. >> >> Back in September 2019 CentOS project launched CentOS Stream as a rolling preview of future RHEL kernels and features, providing an upstream development platform for ecosystem developers that sits between Fedora and RHEL. >> >> Since then the oVirt project tried to keep the software working on Fedora, CenOS Stream, and RHEL/CentOS but it became quickly evident the project lacked resources to keep the project running on three platforms. Further, our user surveys show that oVirt users strongly prefer using oVirt on CentOS and RHEL. >> >> With the upcoming end of life of Fedora 30 the oVirt project has decided to stop trying to keep the pace with this amazing platform, focusing on stabilizing the software codebase on RHEL / CentOS Linux. By focusing our resources and community efforts on RHEL/CentOS Linux and Centos Stream, we can provide better support for those platforms and use more time for moving oVirt forward. >> > > This is a humongous mistake. Almost everything with virtualization and storage starts in Fedora. And there are some configurations that will not be possible in CentOS Stream because of the nature of it. > > As far as the oVirt software keeping up with Fedora, the main problem here has always been that people aren't integrating their software into the distribution itself. That's how everything can get tested together. And this comes back to the old bug about fixing vdsm so that it doesn't use /rhev, but instead something FHS-compliant (RHBZ#1369102). Once that is resolved, pretty much the entire stack can go into Fedora. And then you benefit from the Fedora community being able to use, test, and contribute to the oVirt project. As it stands, why would anyone do this for you when you don't even run on the cutting edge platform that feeds into Red Hat Enterprise Linux? This was actually fixed a long time ago. With this commit: https://github.com/oVirt/vdsm/commit/67ba9c4bc860840d6e103fe604b16f494f60a0… You can configure a compatible vdsm that does not use /rhev. Of course it is not backward compatible, for this we need much more work to support live migration between old and new vdsm using different data-center configurations. > It also seems like the oVirt folks are not learning from the mistakes of the RDO project. They gave up on Fedora several years ago, and wound up spending close to two years playing catchup on Python 3, DNF, modularity, virtualization packaging changes, storage APIs, and everything else all at once. They ground to a halt. They paid a price for not keeping up. And their excuse of unaligned lifecycles stopped being true more than two years ago, when OpenStack's release cycles aligned on Fedora's again. They also proved that Fedora's "churn" wasn't the problem because when push comes to shove, they were able to do something based on Fedora 28 (knowing it was the base for RHEL 8). > > CentOS Stream is worthless in most respects because you aren't really testing or integrating anything new most of the time, you're just making new releases of your software on a stale platform. Again, the purpose of CentOS Stream is to provide a window into the RHEL stream development, which by the nature of things isn't very useful for future-proofing. > > > -- > 真実はいつも一つ！/ Always, there's only one truth! > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/JM5UNXG6YI7R2…

1 0

[JIRA] (OVIRT-2936) lists.ovirt.org is missing in google searches
by Evgheni Dereveanchin (oVirt JIRA) 11 May '20

11 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2936?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2936: ------------------------------------------- Assignee: Marc Dequènes (Duck) (was: infra) > lists.ovirt.org is missing in google searches > --------------------------------------------- > > Key: OVIRT-2936 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2936 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: Marc Dequènes (Duck) > Attachments: signature.asc > > > Hi all, > I now searched google for "engine certificate problems in MacOS", > expecting to find [1], but didn't get it. > I don't think it's due to our robots.txt [2], because google does find > it in [3]. Perhaps it's due to configuration for our site in google or > whatever, no idea. > Can you please handle? Thanks. > [1] https://lists.ovirt.org/archives/list/users@ovirt.org/message/YNL6NSW6GP3IR… > [2] https://lists.ovirt.org/robots.txt > [3] https://www.mail-archive.com/users@ovirt.org/msg60558.html > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2937) Setup account/permissions for ghartuv@redhat.com
by Evgheni Dereveanchin (oVirt JIRA) 11 May '20

11 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2937?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2937: ------------------------------------------- Assignee: Krapali Rai (was: infra) > Setup account/permissions for ghartuv(a)redhat.com > ------------------------------------------------ > > Key: OVIRT-2937 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2937 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Guy Hartuv > Assignee: Krapali Rai > > Hi guys > I am a new employee at Red Hat (SE group - Foundation CI/Release team), and > would like to ask for account/permissions to access: > - https://ovirt-jira.atlassian.net/ > - https://jenkins.ovirt.org/ > Thank you > Guy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

oVirt and Fedora
by Sandro Bonazzola 11 May '20

11 May '20

If you have followed the oVirt project for a few releases you already know oVirt has struggled to keep the pace with the fast innovation cycles Fedora Project is following. Back in September 2019 CentOS project launched CentOS Stream as a rolling preview of future RHEL kernels and features, providing an upstream development platform for ecosystem developers that sits between Fedora and RHEL. Since then the oVirt project tried to keep the software working on Fedora, CenOS Stream, and RHEL/CentOS but it became quickly evident the project lacked resources to keep the project running on three platforms. Further, our user surveys show that oVirt users strongly prefer using oVirt on CentOS and RHEL. With the upcoming end of life of Fedora 30 the oVirt project has decided to stop trying to keep the pace with this amazing platform, focusing on stabilizing the software codebase on RHEL / CentOS Linux. By focusing our resources and community efforts on RHEL/CentOS Linux and Centos Stream, we can provide better support for those platforms and use more time for moving oVirt forward. -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

2 5

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #976
by jenkins＠jenkins.phx.ovirt.org 11 May '20

11 May '20

See <https://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/976/display/re…>

1 3

oVirt infra daily report - unstable production jobs - 1187
by jenkins＠jenkins.phx.ovirt.org 11 May '20

11 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1187//artifact/exported… Cheers, Jenkins

1 0

Re: [oVirt Jenkins] ovirt-system-tests_he-basic-role-remote-suite-master - Build # 406 - Still Failing!
by Yedidyah Bar David 10 May '20

10 May '20

On Sun, May 10, 2020 at 4:35 AM <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… > Build: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… Fails for a long time now, but recently, since he-basic-suite-master is fixed, fails with: https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-role-remote-suite… 03:32:03 TASK [ovirt.hosted_engine_setup : Wait for the local VM] *********************** 04:32:09 fatal: [lago-he-basic-role-remote-suite-master-host-0 -> lago-he-basic-role-remote-suite-master-engine.lago.local]: FAILED! => {"changed": false, "elapsed": 3605, "msg": "timed out waiting for ping module test success: [Errno 24] Too many open files"} Looked around and failed to find other relevant information. I guess we should somehow (in the playbook or in OST, not sure which is better) collect 'ulimit -a' and open files. Searching google for the exact error message (meaning, both that the ping module failed, and that the reason was too many open files), finds only one place, does not seem related, so I do not think it's a regression in ansible. > > > Build Number: 406 > Build Status: Still Failing > Triggered By: Started by timer > > ------------------------------------- > Changes Since Last Success: > ------------------------------------- > Changes for Build #397 > [Sandro Bonazzola] python3: use print function > > > Changes for Build #398 > [Sandro Bonazzola] python3: use print function > > > Changes for Build #399 > [Sandro Bonazzola] python3: use print function > > > Changes for Build #400 > [Sandro Bonazzola] python3: use print function > > > Changes for Build #401 > [Michal Skrivanek] fix list of packages for storage setup > > > Changes for Build #402 > [Lucia Jelinkova] UI test refactoring > > > Changes for Build #403 > [Galit Rosenthal] Remove reposync from upgrade-from-prevrelease-suite-4.3 > > > Changes for Build #404 > [Marcin Sobczyk] selenium: podman: Add grid setup retries > > > Changes for Build #405 > [Marcin Sobczyk] selenium: podman: Add grid setup retries > > > Changes for Build #406 > [Marcin Sobczyk] selenium: podman: Add grid setup retries > > > > > ----------------- > Failed Tests: > ----------------- > No tests ran. -- Didi

2 1

oVirt infra daily report - unstable production jobs - 1186
by jenkins＠jenkins.phx.ovirt.org 10 May '20

10 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1186//artifact/exported… Cheers, Jenkins

1 0

oVirt infra daily report - unstable production jobs - 1185
by jenkins＠jenkins.phx.ovirt.org 09 May '20

09 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1185//artifact/exported… Cheers, Jenkins

1 0

[oVirt Jenkins] cleanup-gated-ovirt-master - Build #145 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 08 May '20

08 May '20

Build: https://jenkins.ovirt.org/job/cleanup-gated-ovirt-master/145/ Build Name: #145 Build Status: FAILURE Gerrit change: null - title: null - project: null - branch: null - author: null <null>

1 0

oVirt infra daily report - unstable production jobs - 1184
by jenkins＠jenkins.phx.ovirt.org 08 May '20

08 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1184//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 108805,2 (ovirt-engine) failed "ovirt-4.3" system tests
by oVirt Jenkins 07 May '20

07 May '20

Change 108805,2 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/108805/2 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3393/

1 0

[JIRA] (OVIRT-2938) port mirrorchecker to Prometheus
by Evgheni Dereveanchin (oVirt JIRA) 07 May '20

07 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2938?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2938: ------------------------------------------- Assignee: Shlomi Zidmi (was: infra) > port mirrorchecker to Prometheus > -------------------------------- > > Key: OVIRT-2938 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2938 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Shlomi Zidmi > > We currently use ovirt-mirrorchecker to check mirror health. It is queried by Nagios. > Since we're moving to Prometheus, it should be adapted to present data consumable by this monitoring tool so that we can get JIRA tickets on stale mirrors. > The code is here: > https://gerrit.ovirt.org/#/admin/projects/ovirt-mirrorchecker > The tool itself should be here: > https://gerrit.ovirt.org/#/admin/projects/mirrorchecker > It runs on OpenShift in the following project: > https://shift.ovirt.org:8443/console/project/ovirt-mirrorchecker/overview -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2938) port mirrorchecker to Prometheus
by Evgheni Dereveanchin (oVirt JIRA) 07 May '20

07 May '20

Evgheni Dereveanchin created OVIRT-2938: ------------------------------------------- Summary: port mirrorchecker to Prometheus Key: OVIRT-2938 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2938 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra We currently use ovirt-mirrorchecker to check mirror health. It is queried by Nagios. Since we're moving to Prometheus, it should be adapted to present data consumable by this monitoring tool so that we can get JIRA tickets on stale mirrors. The code is here: https://gerrit.ovirt.org/#/admin/projects/ovirt-mirrorchecker The tool itself should be here: https://gerrit.ovirt.org/#/admin/projects/mirrorchecker It runs on OpenShift in the following project: https://shift.ovirt.org:8443/console/project/ovirt-mirrorchecker/overview -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

Build failed in Jenkins: deploy-to_ovirt-master_tested #10940
by jenkins＠jenkins.phx.ovirt.org 07 May '20

07 May '20

See <https://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/10940/display/r…> Changes: ------------------------------------------ [...truncated 17.36 KB...] + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + sleep 5 + (( i++ )) + (( i < 180 )) + echo 'Timed out waiting for lock' Timed out waiting for lock + exit 1 Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 3623 killed; [ssh-agent] Stopped.

2 2

[CQ]: 108714, 4 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 07 May '20

07 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108714,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 108810,1 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108810,1 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108714/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3391/

1 0

[CQ]: 108711, 4 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 07 May '20

07 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108711,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 108810,1 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108810,1 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108711/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3387/

1 0

oVirt 4.4.0 First Release Candidate is now available for testing!
by Sandro Bonazzola 07 May '20

07 May '20

The oVirt Project is excited to announce the availability of the first Release Candidate of oVirt 4.4.0 for testing, as of May 6th, 2020 This release unleashes an altogether more powerful and flexible open source virtualization solution that encompasses hundreds of individual changes and a wide range of enhancements across the engine, storage, network, user interface, and analytics on top of oVirt 4.3. Important notes before you try it Please note this is a pre-release build. The oVirt Project makes no guarantees as to its suitability or usefulness. This pre-release must not to be used in production. Some of the features included in oVirt 4.4.0 Release Candidate require content that will be available in CentOS Linux 8.2 but can’t be tested on RHEL 8.2 beta yet due to some incompatibility in openvswitch package shipped in CentOS Virt SIG which requires to rebuild openvswitch on top of CentOS 8.2. Installation instructions For the engine: either use appliance or: - Install CentOS Linux 8 minimal from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - dnf module enable -y javapackages-tools pki-deps postgresql:12 - dnf install ovirt-engine - engine-setup For the nodes: Either use oVirt Node ISO or: - Install CentOS Linux 8 from http://centos.mirror.garr.it/centos/8.1.1911/isos/x86_64/CentOS-8.1.1911-x8… ; select minimal installation - dnf install https://resources.ovirt.org/pub/yum-repo/ovirt-release44-pre.rpm - dnf update (reboot if needed) - Attach the host to engine and let it be deployed. What’s new in oVirt 4.4.0 Release Candidate? - Hypervisors based on CentOS Linux 8 (rebuilt from award winning RHEL8), for both oVirt Node and standalone CentOS Linux hosts - Easier network management and configuration flexibility with NetworkManager - VMs based on a more modern Q35 chipset with legacy seabios and UEFI firmware - Support for direct passthrough of local host disks to VMs - Live migration improvements for High Performance guests. - New Windows Guest tools installer based on WiX framework now moved to VirtioWin project - Dropped support for cluster level prior to 4.2 - Dropped SDK3 support - 4K disks support only for file based storage. iSCSI/FC storage do not support 4k disks yet. - Exporting a VM to a data domain - Editing of floating disks - Integrating ansible-runner into engine, which allows a more detailed monitoring of playbooks executed from engine - Adding/reinstalling hosts are now completely based on Ansible - The OpenStack Neutron Agent cannot be configured by oVirt anymore, it should be configured by TripleO instead This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 8.1 * CentOS Linux (or similar) 8.1 * oVirt Node 4.4 based on CentOS Linux 8.1 (available for x86_64 only) See the release notes [1] for installation instructions and a list of new features and bugs fixed. If you manage more than one oVirt instance, OKD or RDO we also recommend to try ManageIQ <http://manageiq.org/>. In such a case, please be sure to take the qc2 image and not the ova image. Notes: - oVirt Appliance is already available for CentOS Linux 8 - oVirt Node NG is already available for CentOS Linux 8 Additional Resources: * Read more about the oVirt 4.4.0 release highlights: http://www.ovirt.org/release/4.4.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] http://www.ovirt.org/release/4.4.0/ [2] http://resources.ovirt.org/pub/ovirt-4.4-pre/iso/ -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/> [image: |Our code is open_] <https://www.redhat.com/en/our-code-is-open> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

1 0

[JIRA] (OVIRT-2936) lists.ovirt.org is missing in google searches
by Marc Dequènes (Duck) (oVirt JIRA) 07 May '20

07 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2936?page=com.atlassian.jira.… ] Marc Dequènes (Duck) updated OVIRT-2936: ---------------------------------------- Attachment: signature.asc Quack, On 5/6/20 7:27 PM, Yedidyah Bar David wrote: > I now searched google for "engine certificate problems in MacOS", > expecting to find [1], but didn't get it. I added "ovirt" and also quoted the whole title but can only find the www.mail-archive.com link indeed. > I don't think it's due to our robots.txt [2], because google does find > it in [3]. Perhaps it's due to configuration for our site in google or > whatever, no idea. The robots.txt looks fine. I do not think we have any specific Google setting done, at least not by me. Folks, any idea? \_o< > lists.ovirt.org is missing in google searches > --------------------------------------------- > > Key: OVIRT-2936 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2936 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > Attachments: signature.asc > > > Hi all, > I now searched google for "engine certificate problems in MacOS", > expecting to find [1], but didn't get it. > I don't think it's due to our robots.txt [2], because google does find > it in [3]. Perhaps it's due to configuration for our site in google or > whatever, no idea. > Can you please handle? Thanks. > [1] https://lists.ovirt.org/archives/list/users@ovirt.org/message/YNL6NSW6GP3IR… > [2] https://lists.ovirt.org/robots.txt > [3] https://www.mail-archive.com/users@ovirt.org/msg60558.html > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 108617, 4 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 07 May '20

07 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108617,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 108673,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108673,3 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108617/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108673/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3383/

1 0

[CQ]: 108713, 4 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 07 May '20

07 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108713,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 108810,1 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108810,1 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108713/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3379/

1 0

oVirt infra daily report - unstable production jobs - 1183
by jenkins＠jenkins.phx.ovirt.org 07 May '20

07 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1183//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 108854,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 07 May '20

07 May '20

Change 108854,3 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/108854/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23565/

1 0

[CQ]: 108712, 4 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 06 May '20

06 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108712,4 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 108810,1 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108810,1 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108712/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3375/

1 0

[CQ]: 108696, 2 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 06 May '20

06 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108696,2 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 108810,1 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108810,1 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108696/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3371/

1 0

[JIRA] (OVIRT-2937) Setup account/permissions for ghartuv@redhat.com
by Guy Hartuv (oVirt JIRA) 06 May '20

06 May '20

Guy Hartuv created OVIRT-2937: --------------------------------- Summary: Setup account/permissions for ghartuv(a)redhat.com Key: OVIRT-2937 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2937 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Guy Hartuv Assignee: infra Hi guys I am a new employee at Red Hat (SE group - Foundation CI/Release team), and would like to ask for account/permissions to access: - https://ovirt-jira.atlassian.net/ - https://jenkins.ovirt.org/ Thank you Guy -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 108760,3 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 06 May '20

06 May '20

Change 108760,3 (ovirt-imageio) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/108760/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23553/

1 0

[CQ]: 108816, 1 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 06 May '20

06 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108816,1 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 108810,1 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108810,1 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108816/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3367/

1 0

[JIRA] (OVIRT-2936) lists.ovirt.org is missing in google searches
by Yedidyah Bar David (oVirt JIRA) 06 May '20

06 May '20

Yedidyah Bar David created OVIRT-2936: ----------------------------------------- Summary: lists.ovirt.org is missing in google searches Key: OVIRT-2936 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2936 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi all, I now searched google for "engine certificate problems in MacOS", expecting to find [1], but didn't get it. I don't think it's due to our robots.txt [2], because google does find it in [3]. Perhaps it's due to configuration for our site in google or whatever, no idea. Can you please handle? Thanks. [1] https://lists.ovirt.org/archives/list/users@ovirt.org/message/YNL6NSW6GP3IR… [2] https://lists.ovirt.org/robots.txt [3] https://www.mail-archive.com/users@ovirt.org/msg60558.html -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2935) Jenkins succeeded, Code-Review +1
by Barak Korren (oVirt JIRA) 06 May '20

06 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2935?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2935: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Jenkins succeeded, Code-Review +1 > --------------------------------- > > Key: OVIRT-2935 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2935 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: Evgheni Dereveanchin > > It is nice to get good review from Jeknins, but I don't think it is smart enough > to do code review, and it should really use Continuous-Integration+1. > Jenkins CI > Patch Set 2: Code-Review+1 > Build Successful > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/2772/ : SUCCESS > See https://gerrit.ovirt.org/c/108772/2#message-6225787b_94ed3eac -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2935) Jenkins succeeded, Code-Review +1
by Barak Korren (oVirt JIRA) 06 May '20

06 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2935?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2935: ------------------------------------- It seems the Gerrit trigger configuration was reset to its default configuration instead of our custom one. I restored it manually. [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794] please find out the RC for this. > Jenkins succeeded, Code-Review +1 > --------------------------------- > > Key: OVIRT-2935 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2935 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > It is nice to get good review from Jeknins, but I don't think it is smart enough > to do code review, and it should really use Continuous-Integration+1. > Jenkins CI > Patch Set 2: Code-Review+1 > Build Successful > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/2772/ : SUCCESS > See https://gerrit.ovirt.org/c/108772/2#message-6225787b_94ed3eac -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2935) Jenkins succeeded, Code-Review +1
by Ehud Yonasi (oVirt JIRA) 06 May '20

06 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2935?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2935: ------------------------------------ I am looking into it right now > Jenkins succeeded, Code-Review +1 > --------------------------------- > > Key: OVIRT-2935 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2935 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > It is nice to get good review from Jeknins, but I don't think it is smart enough > to do code review, and it should really use Continuous-Integration+1. > Jenkins CI > Patch Set 2: Code-Review+1 > Build Successful > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/2772/ : SUCCESS > See https://gerrit.ovirt.org/c/108772/2#message-6225787b_94ed3eac -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[JIRA] (OVIRT-2935) Jenkins succeeded, Code-Review +1
by Barak Korren (oVirt JIRA) 06 May '20

06 May '20

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2935?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2935: ------------------------------------- Looks liks someone messed up the Gerrit trigger configuration, [~accountid:5aa0f39f5a4d022884128a0f], [~accountid:5dbc31f88704ba0dab2444b3], [~accountid:557058:caa507e4-2696-4f45-8da5-d2585a4bb794], [~accountid:557058:5ca52a09-2675-4285-a044-12ad20f6166a] any idea? > Jenkins succeeded, Code-Review +1 > --------------------------------- > > Key: OVIRT-2935 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2935 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Nir Soffer > Assignee: infra > > It is nice to get good review from Jeknins, but I don't think it is smart enough > to do code review, and it should really use Continuous-Integration+1. > Jenkins CI > Patch Set 2: Code-Review+1 > Build Successful > https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/2772/ : SUCCESS > See https://gerrit.ovirt.org/c/108772/2#message-6225787b_94ed3eac -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

[CQ]: 108693, 9 (vdsm) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 06 May '20

06 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108693,9 (vdsm) failed. However, this change seems not to be the root cause for this failure. Change 108810,1 (vdsm) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108810,1 (vdsm) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108693/9 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3363/

1 0

[JIRA] (OVIRT-2935) Jenkins succeeded, Code-Review +1
by Nir Soffer (oVirt JIRA) 06 May '20

06 May '20

Nir Soffer created OVIRT-2935: --------------------------------- Summary: Jenkins succeeded, Code-Review +1 Key: OVIRT-2935 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2935 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Nir Soffer Assignee: infra It is nice to get good review from Jeknins, but I don't think it is smart enough to do code review, and it should really use Continuous-Integration+1. Jenkins CI Patch Set 2: Code-Review+1 Build Successful https://jenkins.ovirt.org/job/ovirt-imageio_standard-check-patch/2772/ : SUCCESS See https://gerrit.ovirt.org/c/108772/2#message-6225787b_94ed3eac -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126)

1 0

Install of new ovirt baremetal system 4.3.9
by kelley bryan 06 May '20

06 May '20

Engine deployment fails near end: [ ERROR ] fatal: [localhost]: FAILED! => {"changed": true, "cmd": "set -euo pipefail && firewall-cmd --get-active-zones | grep -v \"^\\s*interfaces\"", "delta": "0:00:00.352904", "end": "2020-05-05 22:28:01.561606", "msg": "non-zero return code", "rc": 1, "start": "2020-05-05 22:28:01.208702", "stderr": "", "stderr_lines": [], "stdout": "", "stdout_lines": []} The system may not be provisioned according to the playbook results: please check the logs for the issue, fix accordingly or re-deploy from scratch.\n"} were does ovirt store logs?

1 0

[CQ]: 108810,1 (vdsm) failed "ovirt-4.3" system tests
by oVirt Jenkins 06 May '20

06 May '20

Change 108810,1 (vdsm) is probably the reason behind recent system test failures in the "ovirt-4.3" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/108810/1 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3359/

1 0

[CQ]: 108666, 4 (ovirt-engine) failed "ovirt-4.3" system tests, but isn't the failure root cause
by oVirt Jenkins 06 May '20

06 May '20

A system test invoked by the "ovirt-4.3" change queue including change 108666,4 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 108673,3 (ovirt-engine) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 108673,3 (ovirt-engine) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/108666/4 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/108673/3 For failed test results see: https://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/3355/

1 0

oVirt infra daily report - unstable production jobs - 1182
by jenkins＠jenkins.phx.ovirt.org 06 May '20

06 May '20

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - https://jenkins.ovirt.org/job/system_jenkins-report/1182//artifact/exported… Cheers, Jenkins

1 0

[CQ]: 108774,5 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 05 May '20

05 May '20

Change 108774,5 (ovirt-engine) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/108774/5 For failed test results see: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/23549/

1 0