- Infra - oVirt List Archives

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

07 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 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/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) 06 May '20

06 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